From invoice
to official record.
Submit invoices, credit notes, and debit notes. Send line items and prices; the API calculates totals and prepares your documents.
THE ETA INTEGRATION LAYER
Egyptian e-invoicing, built into your product. One API for invoices, receipts, and the customers who depend on you.
Start in sandbox. Go live when you’re ready.
Example Trading Co.
Illustrative workflow · no documents are sent
Built for the teams
building business software.
ONE PLATFORM, THE FULL PICTURE
Keep your product at the center. AVTAX handles the connection between your business data and the Egyptian Tax Authority.
Submit invoices, credit notes, and debit notes. Send line items and prices; the API calculates totals and prepares your documents.
Connect sales and return receipts to ETA, with device-based receipt linking and status checks when a submission needs a second look.
Manage customer registrations, API keys, document limits, and signing connections from your partner portal.
A CLEAR PATH TO ETA
From the first API request to the latest document status, give your integration a workflow you can follow.
Your signing key stays with you.
Documents are signed through AVTAX Bridge using the customer’s local USB token.
Submit invoice or receipt data as JSON using the customer’s API key.
POST /api/Invoices/submitAVTAX calculates totals, prepares the ETA format, and requests the signature from the connected device.
Get document identifiers and individual submission outcomes, including errors that need your attention.
Configure callbacks to receive ETA status notifications at your own endpoint.
Read about webhooksMADE FOR DEVELOPERS
A straightforward HTTP API with interactive documentation. Use the tools you already know and keep the experience inside your own product.
# Submit a customer invoice
curl --request POST \
'https://eta-api.avtax.net/api/Invoices/submit' \
--header 'X-Api-Key: YOUR_CUSTOMER_API_KEY' \
--header 'Content-Type: application/json' \
--data @invoice.json
Use your customer’s API key and an invoice JSON payload .
# Submit a customer receipt
curl --request POST \
'https://eta-api.avtax.net/api/Receipts/submit' \
--header 'X-Api-Key: YOUR_CUSTOMER_API_KEY' \
--header 'Content-Type: application/json' \
--data @receipt.json
Use your customer’s API key and a receipt JSON payload .
ROOM TO BUILD. ROOM TO GROW.
Test the complete integration with ETA preproduction, then move to a production setup that fits your customer base.
Create your partner accountRegister a sandbox customer, connect the signing app, and test document submissions against ETA preproduction.
Manage production customers with document allowances tailored to your business. Sandbox and production registrations stay separate.
A FEW THINGS TO KNOW
More implementation details are in the integration guide.
No. AVTAX is an API layer between your existing software and ETA. Your application sends document data over HTTP and uses the returned results in its own workflow.
AVTAX Bridge runs on the customer’s Windows device and signs through their USB token. The signing key stays on that token. The bridge must be connected when a signature is requested.
Yes. Register the customer in sandbox with their ETA preproduction credentials. You can maintain a separate production registration for the same Tax ID when you are ready to go live.
Yes. Your partner workspace brings customer registrations, API keys, document limits, and signing connections together. The Partner Management API also lets you build these operations into your own tools.
Submission and validation are separate steps. Check each document’s result, then use status endpoints or configured webhooks to follow ETA’s validation outcome. A received document can still be marked invalid.
YOUR NEXT INTEGRATION STARTS HERE