Avtax ETA API Documentation

The Avtax ETA API is a B2B gateway for integrating with the Egyptian Tax Authority (ETA). It handles the full document lifecycle — from JSON input to a cryptographically signed, ETA-compliant document — so your team can focus on business logic, not tax compliance.

Authentication

The Avtax ETA API uses two authentication schemes depending on which API group you are calling.

Obtaining a JWT Token (Partner API)

POST /api/Auth/login
Content-Type: application/json

{
  "email": "partner@yourcompany.com",
  "password": "your-password"
}

{
  "success": true,
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expiration": "2026-02-01T00:00:00Z",
  "message": "Login successful"
}

Using the X-Api-Key (Document API)

Each customer has a unique API key generated via POST /api/Customers/{id}/api-keys. Provide it in the X-Api-Key header for all Invoice and Receipt requests.

X-Api-Key: a1b2c3d4e5f6...

Quick Start — Submit an Invoice

The following example submits a simple B2B invoice for a registered customer. Use the customer's X-Api-Key (from POST /api/Customers/{id}/api-keys) in the request header.

POST /api/Invoices/submit
X-Api-Key: <customer-api-key>
Content-Type: application/json

{
  "invoices": [
    {
      "internalID": "INV-2026-0001",
      "dateTimeIssued": "2026-01-15T10:00:00Z",
      "documentType": "I",
      "taxpayerActivityCode": "4620",
      "receiver": {
        "type": "B",
        "id": "012345678",
        "name": "Client Company LLC"
      },
      "invoiceLines": [
        {
          "description": "Software Development Services",
          "itemType": "EGS",
          "itemCode": "EG-123456789-12345",
          "unitType": "EA",
          "quantity": 1,
          "unitValue": {
            "currencySold": "EGP",
            "amountEGP": 10000
          }
        }
      ]
    }
  ]
}

Partner Auth

Manage partner account registration and login. All endpoints in this group return a JWT token used to authenticate Partner API calls.

{
  "partnerName": "My Integration Co.",
  "email": "partner@example.com",
  "password": "SecurePassword1!",
  "phoneNumber": "+201000000000"
}

Customer Management

Register and manage customer ERPs under your partner account. All endpoints require a Authorization: Bearer <token> header. Each customer gets an isolated API key used for document submission.

API Key Management

Each customer requires an active API key to submit documents. Generating a new key automatically revokes the previous one.

ETA Notification Forwarding

Avtax ETA API acts as a relay between ETA and your customer's ERP system. ETA calls our callback URLs, we receive the notification, transform it into a simple JSON format, and POST it to the URL your customer registered.

What your customer's ERP receives

Your customer's ERP endpoint receives a POST request with this simplified JSON body. They must return 200 to acknowledge receipt.

{
  "source": "ETA",
  "type": "document",
  "deliveryId": "838847HS2",
  "receivedAt": "2026-01-15T10:00:00Z",
  "notifications": [
    {
      "eventType": "document-validated",
      "uuid": "F9D425P6DS7D8IU",
      "internalId": "INV-2026-0001",
      "submissionId": "JU7GH07JNA23N",
      "status": "Valid"
    }
  ]
}

{
  "companyName": "My Client LLC",
  "branchCode": "0",
  "etaClientId": "your-eta-client-id",
  "etaClientSecret": "your-eta-client-secret",
  "isProduction": false
}

Invoice Submission

Submit standard invoices, credit notes, and debit notes to the Egyptian Tax Authority. All document types flow through a single endpoint using the documentType field. All endpoints require an X-Api-Key header.

Document Types

Receipt Submission

Submit B2C receipts and return receipts. Receipts use device-based chain linking — each device maintains its own sequential chain automatically tracked by the API. All endpoints require an X-Api-Key header.

ETA Notifications

Avtax ETA API acts as a relay for ETA event notifications. We receive raw ETA callbacks on behalf of your customers, transform them into a clean JSON format, and forward them directly to each customer's registered ERP endpoint — so your customers never need to expose an ETA-compatible server themselves.

Setup — 3 Steps

Outbound Notification Payload

This is what the customer's ERP endpoint receives for both document and receipt events. The type field distinguishes between the two.

POST https://customer-erp.com/eta-notifications
Content-Type: application/json

{
  "source": "ETA",
  "type": "document",
  "deliveryId": "838847HS2",
  "receivedAt": "2026-01-15T10:00:00Z",
  "notifications": [
    {
      "eventType": "document-validated",
      "uuid": "F9D425P6DS7D8IU",
      "internalId": "INV-2026-0001",
      "submissionId": "JU7GH07JNA23N",
      "status": "Valid"
    }
  ]
}

POST https://customer-erp.com/eta-notifications
Content-Type: application/json

{
  "source": "ETA",
  "type": "receipt",
  "deliveryId": "929157AB1",
  "receivedAt": "2026-01-15T11:30:00Z",
  "notifications": [
    {
      "eventType": "Validated",
      "uuid": "9d74ecc5a844354864c762c0d413ee42336561f5",
      "internalId": "REC-2026-0042",
      "submissionId": "BC6J9M86WWVP567DEYGFTD8G10",
      "status": "Invalid"
    }
  ]
}

Field Reference

Error Codes

All errors return a consistent JSON structure with success, message, errorCode, and an errors array.

HTTP Status Codes

Internal Error Codes (errorCode field)