Technical Adjustments Required on ERP side

To ensure the proper operation of the solution WDC Translator, the following technical actions are required from implementer's side (ERP).

Implementation Notes

[27/02/26]

Change: For security reasons, the authentication using apikey field must be included in the header of the POST request.
Due to security policies and protocol restrictions, including the ClientId field in the request body is neither permitted nor technically supported.

[30/01/26]

JSON Enrichment: Implement ClientId field in all request payloads

API Endpoint: Update to new API endpoints (UAT & Production)

Full PDF Generation: Implement full PDF generation with all mandatory elements (QR Code, MARK, UID, AUTH CODE, Provider info)
QR Code: Implement both standard and offline QR Code generation

Upload FULL PDF: Implement PDF upload via POST: /Invoice/file endpoint

Additional Notes: Remove token issuance process and API Request:GET status

1. JSON Enrichment

You are required to enrich the request header by adding the following field:

apikey

Value: apikey used for authentication

Theapikey must be included in the header of every POST request

JSON example:"apikey": "your-api-key-here"

2. API Endpoint Changes

Please update your integration to use the following endpoints apidomain/invoice/wdc.

POST request

Demo (UAT)
https://einvoiceapiuat.impact.gr/invoice/wdc

Production
https://einvoiceapi.impact.gr/invoice/wdc

Response Structure

The apidomain/invoice/wdc endpoint returns a response with the following fields:

status

processUniqueID

erpUniqueCode

invoiceDate

issuerVRN

mark - Returned only in case of a successful submission

uid - Document ID (SHA-1), assigned by AADE

authenticationCode - Authentication string, assigned by AADE only when using an Electronic Invoicing Provider

errors - Error codes with corresponding descriptions (if any)

10.

qrCodeUrl - URL used for QR Code generation and visualization

JSON Response Example

Success Response

Failed Response

Status Values

The status field can have the following values:

InProcess = 1

NotFound = 2

Success = 3

Failed = 4

3. Full PDF Generation

Your generated PDF documents must include all mandatory elements required by the provider in order to allow the Upload full PDF process.

The PDF must contain:

QR Code

MARK

UID

AUTH CODE

Provider name and provider URL

Provider license number

PDF & QRCode Requirements

The QR Code must be generated based on the URL returned by the API, in accordance with the official specifications and visualization requirements described in the documentation Mandatory Printing Fields

In offline operation scenarios, an Offline QR Code must be generated.

4. Upload FULL PDF via REST API

Submit the full PDF document through a REST API call, following the same approach already applied by companies operating in the eInvoicing ecosystem (Elise).

Specifically, the POST:Invoice/file API endpoint must be used, in accordance with the technical specifications described here:
https://developers.s1ecos.com/invoice-document-upload-invoicefile-869837m0

5. Additional Notes

The existing token issuance process is deprecated and will no longer be used.

For API Get Status operations:

The same POST REQUEST:apidomain/invoice/wdc is re-submitted using the same invoice data.

The WDC response remains unchanged and is returned in its current format.

Elise - WDC Translator

Technical Adjustments Required on ERP side#

Implementation Notes#

1. JSON Enrichment#

2. API Endpoint Changes#

POST request#

Response Structure#

JSON Response Example#

Status Values#

3. Full PDF Generation#

PDF & QRCode Requirements#

4. Upload FULL PDF via REST API#

5. Additional Notes#