Integrate Fatoora with ERP, POS, and other systems

What you can integrate today: local signer Bearer API, browser session APIs under /api/t/{slug}, and customization for ERP connectors — with concrete endpoints.

e-invoice API EgyptFatoora integrationsigner pending signed APIربط ERP فاتورة إلكترونيةERP connector Egypt

Fatoora today has two integration surfaces that exist in code: the local signer machine API (Bearer key) and the browser session APIs under `/api/t/{slug}/…`. A general ERP push API key for third-party servers is not shipped as a public product feature yet — use customization when you need deep ERP connectors (Customize).

A. Local signer integration (supported now)

Any process that can call HTTP with the tenant signer API key can participate in signing:

• `GET {origin}/api/e-invoicing/signer/pending`
• `POST {origin}/api/e-invoicing/signer/signed`
• Header: `Authorization: Bearer {signerApiKey}`
• Aliases without the `e-invoicing` segment also exist under `/api/signer/*`

This is how the official desktop signer works. Do not expose the signer key in front-end JavaScript.

B. Tenant APIs (session cookie)

Human operators and authenticated browser sessions use `eta_saas_session`. Routes include settings, documents (create, ready, submit, refresh, pdf, cancel, duplicate), customers, products, users, inbound, and imports. Roles: write for OWNER/ADMIN/ACCOUNTANT; settings for OWNER/ADMIN.

These routes are not intended as an unattended ERP API without a session. For server-to-server ERP sync, request a customization / connector.

C. Typical ERP pattern with Fatoora

• ERP keeps commercial invoices
• Middleware or customization creates Fatoora documents (customers/products synced first)
• Fatoora marks Ready to sign
• Local signer signs with USB token
• Fatoora submits to ETA and stores uuid/status/PDF
• ERP stores ETA uuid / Valid status from callbacks or polling built in a connector

D. What to configure before integrating

• Working Test ETA login
• Stable document prefix/sequence policy
• Signer key distribution to signing PCs only
• Import of master data
• Preprod end-to-end proof before Prod credentials

Next steps

• Product path: Getting started
• Commercial path for connectors: /customize or /demo