Invoice/secure - eINVOICING

The specific API call was introduced for security purposes, ensuring that the payload is transmitted entirely in encrypted form using PGP Encryption, in order to safeguard sensitive data.

The transmission flow follows the same approach as the standard invoice/json process. However, before sending the request, the client encrypts the payload using the provider’s public encryption key.
Flow Steps:
1.Create Payload
2.Encrypt using the provider’s public key
3.Send API Request
4.Provider decrypts the payload using Client private key

For the implementation, you will need to coordinate with us to receive the required technical details, including the provider’s public key.

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢201Created

application/json

Created

Body

Example

{
    "success": true,
    "message": "string",
    "statusCode": "string",
    "integritySignature": "string",
    "signature": "string",
    "uid": "string",
    "mark": 0,
    "cancellationMark": 0,
    "authenticationCode": "string",
    "myDataResponse": "string",
    "status": "UNKNOWN",
    "series": "string",
    "number": "string",
    "dateIssued": "2019-08-24T14:15:22.123Z",
    "domain": "string",
    "url": "string",
    "qrCodeString": "string",
    "erpQrCode": "string",
    "uniqueId": "string",
    "internalId": "string"
}

🟠400Bad Request

🟠401Unauthorized

🟠408Request Timeout

🟠409Conflict

🔴500Internal Server Error