einvo API
einvo connects your ERP to the UAE e-invoicing system: it validates documents against PINT AE and the UAE Tax Data Document rules, delivers them over the Peppol network (corner 2) and reports the tax data to the Federal Tax Authority (FTA). Documents you receive arrive in your inbox and on your webhook.
API keys with scopes, expiry and revoke; OAuth client credentials.
Submit a UBLSend PINT AE UBL from your ERP, follow its status, receive documents.
Billing APILet einvo build the UBL: customers, drafts, issuing, PINT AE scenarios.
WebhooksSigned events for received documents, status and FTA changes.
SandboxValidate everything, send nothing: test keys for development and CI.
API referenceEvery endpoint and schema, generated from the OpenAPI spec.
Quick start
- A company administrator opens Administration → API keys in the portal and creates a
sandbox key with the
documents:writeanddocuments:readscopes. The key (ek_test_…) is shown once. - Check the key:
curl https://api.einvo.ae/api/v1/me -H "Authorization: Bearer $EINVO_API_KEY"
- Submit a PINT AE invoice. In sandbox it is validated and stored, never sent:
curl 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 @invoice.xml
- Read the validation result in the response (
status,issues), fix, repeat. When it passes, create a live key (ek_live_…) and the same call delivers the invoice over Peppol and reports it to the FTA.
Basics
| Base URL | https://api.einvo.ae |
|---|---|
| Format | JSON (UTF-8); UBL documents as application/xml |
| Authentication | Authorization: Bearer ek_live_… (or X-API-Key) · details |
| Errors | RFC 9457 application/problem+json with a stable code · list |
| Limits | 600 requests per minute per key · details |
| Spec | openapi.json (OpenAPI 3.1) · Postman collection |
| SDKs | Java, .NET, Python, Node.js · SDKs |
Which API do I need?
- Your ERP already produces PINT AE UBL (SAP, Oracle, Dynamics with an e-invoicing add-on): use Submit a UBL.
- Your system has invoice data but no UBL: post simplified JSON to the same endpoint, or use the billing API, where einvo keeps the customer and product master data, numbers the invoices without gaps and renders the bilingual PDF.
- You receive invoices: subscribe to
document.receivedwebhooks or poll the inbox.
Questions: developers@einvo.ae. The API is versioned in the path (/api/v1); additive changes
(new fields, endpoints, events) happen without a new version, so ignore unknown JSON fields.