Developers

Invoice data via API, straight into your systems.

Everything Alya Books can do is also available through the API: create, submit, deliver and receive e-invoices. One REST API for any ERP or custom system, JSON-based, fully documented, with test keys that never touch the live tax system.

Read the docs Get an API key

REST · JSON · HTTPS
153 operations
27 webhook events
MCP · 138 tools
CLI

curl -X POST https://api.alyabooks.ai/api/v1/invoices \
  -H "X-API-KEY: sk_test_…" -H "Content-Type: application/json" -d '{
    "buyer": { "name": "Al Noor Trading LLC", "trn": "100234567890003", "emirate": "DXB" },
    "issueDate": "2027-01-12",
    "lines": [{ "description": "Consulting, January", "quantity": 10, "unitPrice": 500, "taxCategory": "standard" }],
    "submit": true
  }'

Status quo

Manual data handoffs cost hours every day.

No real-time data

Invoices sit in inboxes or wait for manual handovers before the ERP can process them.

Error-prone imports

CSV exports, manual uploads and incorrect field data regularly lead to rework, and to rejected submissions.

No status transparency

Without automatic feedback it stays unclear which invoices were reported, delivered or rejected.

Core capabilities

One API for the entire invoice process.

Outgoing invoices

01
Create, validate, submit
One request creates the invoice, checks it against PINT AE and, with submit: true, hands it to the ASP. Batch creation included.
02
Status and webhooks
Status with the ASP and FTA timeline on request; invoice.reported, invoice.rejected, invoice.paid and more pushed to your endpoint.

Incoming invoices

01
Import and validate
Upload XML, PDF or images through the API; the validation report comes back with the import.
02
Read the contents
Totals, lines, taxes and attachments of imported invoices are available as JSON sub-resources.

Result: your system talks to Alya Books. Both directions, one contract, no manual work.

API and automation

The API adapts to existing processes.

Developer-first: full control

Invoices, recurring invoices, customers, products, projects, VAT, payment links, bank feeds and webhooks are documented REST endpoints with an OpenAPI document you can generate clients from.

OpenAPI 3
llms.txt

ERP integration: upstream validation

Alya Books adds structured checks and FTA reporting to existing ERP processes without changing established flows. Connectors for QuickBooks, Xero, Odoo and Zoho Books ship ready-made.

Connectors
Exports

AI integration: MCP server with 138 tools

Connect Claude, other assistants and your own agents directly to Alya Books: create, check, submit and reconcile invoices from a conversation, with the same keys and scopes.

MCP
Agents
CLI

How companies use Alya Books

E-invoicing inside their own product.

Software and ERP vendors embed Alya Books as their UAE e-invoicing layer: outgoing invoices are produced in PINT AE and reported through the API, incoming invoices come back validated, webhooks keep both systems in sync. Their interface stays in place while Alya Books works in the background. Accountancy firms use one key with X-Organization-Id to act for many clients.

Technical specification

Open. Stable. Well documented.

REST API

JSON · HTTPS · API key header · test and live environments · scopes · rate limits · request log

Format

PINT AE (UBL 2.1) for all document types; JSON in, XML and PDF out

Webhooks

27 events · HMAC-SHA256 signatures · retries with back-off · delivery log · test deliveries

Tooling

MCP server (138 tools) · @alyabooks/cli · OpenAPI · AGENTS.md for coding agents

/docs
/docs/api-reference/openapi.json
/docs/llms.txt
npm: @alyabooks/cli
POST /api/v1/mcp

Start with the getting started guide, then the outgoing invoices guide and the webhooks guide.

Your first invoice via API in minutes.

Generate a test key, send a request, invoice created. Switch to a live key when you go live.

Get an API key Read the docs

Public documentation · Test keys never reach the FTA