Submit a UBL
Your ERP produces a PINT AE UBL 2.1 invoice or credit note; einvo validates it (UBL schema, PINT AE and UAE TDD Schematron),
sends it to the buyer's access point over Peppol AS4 and reports the tax data to the FTA. Scope: documents:write.
curl -i https://api.einvo.ae/api/v1/invoices \
-H "Authorization: Bearer $EINVO_API_KEY" \
-H "Content-Type: application/xml" \
-H "Idempotency-Key: INV-2026-00042" \
--data-binary @INV-2026-00042.xml
HTTP/1.1 202 Accepted
Location: /api/v1/invoices/7c1d1f9e-3a52-4b7e-9d1c-0f3e5b1a2c44
Content-Type: application/json
{
"id": "7c1d1f9e-3a52-4b7e-9d1c-0f3e5b1a2c44",
"direction": "OUTBOUND",
"kind": "INVOICE",
"status": "VALIDATED",
"number": "INV-2026-00042",
"issueDate": "2026-11-19",
"sender": "0235:1987654321",
"receiver": "0235:1345678901",
"currency": "AED",
"totalAmount": 1050.00,
"taxAmount": 50.00,
"ruleset": "PINT-AE 2026.11 / UAE-TDD 1.0.5",
"issues": [],
"sandbox": false
}
- The seller endpoint (
cac:AccountingSupplierParty/cbc:EndpointID, scheme0235+ TIN) must be one of your company's Peppol participants. - Idempotency-Key (recommended, up to 128 characters): resubmitting with the same key returns the original document instead of a duplicate. Use your invoice number.
- An invalid document is stored with
status: REJECTEDand theissueslist (rule id, message, XPath location); it is not sent.
Validate without sending
curl https://api.einvo.ae/api/v1/invoices/validate -H "Authorization: Bearer $EINVO_API_KEY" \
-H "Content-Type: application/xml" --data-binary @invoice.xml
# {"valid":false,"kind":"INVOICE","ruleset":"...","durationMillis":182,
# "issues":[{"severity":"FATAL","ruleId":"ibr-159-ae","message":"...","location":"/Invoice/..."}]}
No UBL? Send JSON
The same endpoint accepts a simplified JSON invoice (Content-Type: application/json); einvo generates the PINT AE UBL.
{
"kind": "INVOICE",
"sellerTin": "1987654321",
"number": "INV-2026-00043",
"issueDate": "2026-11-19",
"currency": "AED",
"transactionFlags": "00000000",
"buyer": { "legalName": "Noor Electronics LLC", "endpointScheme": "0235", "endpointId": "1345678901",
"trn": "100134567890103", "street": "Corniche Road 5", "city": "Abu Dhabi", "emirate": "AE-AZ", "countryCode": "AE" },
"paymentMeansCode": "30",
"iban": "AE070331234567890123456",
"lines": [
{ "name": "Laptop", "itemType": "G", "quantity": 1, "unitCode": "H87", "unitPrice": 1000.00,
"taxCategory": "S", "taxRate": 5, "hsCode": "847130" }
]
}
Follow the status
| Status | Meaning |
|---|---|
VALIDATED | Passed validation, queued for Peppol delivery and FTA reporting |
REJECTED | Failed validation (see issues); fix and resubmit with a new idempotency key |
ROUTED / SENT | Receiver found in the Peppol directory / transmitted over AS4 |
DELIVERED | The receiving access point confirmed delivery |
RECIPIENT_REJECTED | The buyer rejected the document (message level status) |
UNDELIVERABLE / SEND_FAILED | Receiver not on Peppol / transmission failed after retries |
NOT_EXCHANGED | Not exchanged over Peppol by design (buyer not on e-invoicing, VAT group, sandbox); tax data reported where required |
Get GET /api/v1/invoices/{id} (with transmissions, FTA reports and message level statuses), or subscribe to the
document.status and document.fta webhooks instead of polling.
GET /api/v1/invoices/{id}/ubl and /pdf return the stored UBL and the bilingual PDF.
Receive documents
Documents sent to your Peppol participant IDs arrive in the inbox. Scope: documents:read.
# documents not yet acknowledged by your system
curl "https://api.einvo.ae/api/v1/inbox" -H "Authorization: Bearer $EINVO_API_KEY"
# download the UBL, book it in your ERP, then acknowledge so it leaves the list
curl "https://api.einvo.ae/api/v1/invoices/$ID/ubl" -H "Authorization: Bearer $EINVO_API_KEY" -o "$ID.xml"
curl -X POST "https://api.einvo.ae/api/v1/inbox/$ID/ack" -H "Authorization: Bearer $EINVO_API_KEY"