Generic API v1-beta

The /generic endpoints provide a flexible interface for handling business documents when a dedicated document-specific endpoint is not required. In v1-beta, these endpoints can be used to send generic payloads and to respond to them (the latter for testing only).

Send

To send a document, use POST /api/v1-beta/{partyId}/generic/send. The {partyId} in the route is the sender's partyId.

Response

WARNING

Calling this endpoint yourself is optional. If you don't, eConnect automatically acknowledges the sender with an AB 5 minutes after the document was received. Only one MLS reply is allowed per document; see Send an MLS response for the full behavior, including the error returned when a reply was already sent.

To send a response for a received document, use POST /api/v1-beta/generic/{documentId}/response.

• {documentId} is the documentId of the received document.

This endpoint is used for flows such as sending a Peppol Message Level Status (MLS) back to the original sender.

Request body example:

{
  "status": "RE",
  "description": "Document could not be delivery due to connectivity errors.",
  "lines": [
    {
        "statusReasonCode": "FD", 
        "description": "Socket exception"
    }
   ]
}

Typical status values depend on the response flow. For MLS, examples include AP for accepted and RE for rejected.