REST + JSON, no surprises
Predictable resource URLs. Standard HTTP verbs (GET, POST, PATCH, DELETE). JSON request and response bodies. ISO 8601 dates. RFC 3339 datetimes. AED amounts as integer minor units (fils) to avoid floating-point drift.
REST API for every resource. Webhooks for every state change. SDKs for the languages your team already uses. Sandbox is free and open — no signup required to read the contract or try a request. Production API ships with the product in October 2026.
Authentication, base URL, resource catalog, idempotency, rate limits, error codes. The full design spec for the API that ships at launch.
Read the API reference →32 event types across invoicing, payroll, tax, and payments. Signature verification, retry policy, replay endpoint, and per-event payload schemas.
Read the webhooks catalog →If you ship integrations for UAE SMBs — banks, payment gateways, e-commerce platforms, industry verticals — the partner program is where to start.
Apply to the partner program →An ERP is a system of record. The value of a system of record compounds with how easily other systems can read from it and write to it. We learned this watching UAE SMBs lock their data into other UAE accounting tools databases and other UAE accounting tools organizations that resist export. Customers who lose access to their own business data lose leverage — over their vendor, over their auditor, over their own decisions.
HIBR's API exists for three audiences:
Your internal engineering team integrating HIBR with your other tools — your CRM, your e-commerce store, your business intelligence dashboards, your custom workflows.
Independent developers and ISVs shipping HIBR connectors for UAE banks, payment gateways, logistics, and industry-specific apps. The partner program supports these.
Autonomous agents (Claude, GPT-class systems) that need to read invoices, post journal entries, or trigger a VAT 201 calculation as part of a workflow. We treat AI agents as first-class API consumers.
Predictable resource URLs. Standard HTTP verbs (GET, POST, PATCH, DELETE). JSON request and response bodies. ISO 8601 dates. RFC 3339 datetimes. AED amounts as integer minor units (fils) to avoid floating-point drift.
Every state-changing request supports an Idempotency-Key header. Retry-safe, exactly-once semantics on the create side — critical for payment and tax endpoints where a duplicate post means a duplicate invoice at FTA.
API version pinned via Hibr-Version header. Breaking changes get a new version. Old versions live for a minimum 18 months with deprecation notices via webhook + email. We will not silently change response shapes on you.
Every error returns a structured JSON body with a stable code field, a human-readable message, and (where applicable) a field indicating which input was invalid. Error codes are documented and versioned alongside the API.
Per-tier limits published in this document, exposed in response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset). 429 responses always include a Retry-After header. No silent throttling.
Polling is the lazy way to integrate. Every state change in HIBR emits a webhook. Subscribe once, get pushed events forever. Signatures verifiable with HMAC-SHA256. Replays available via API for 30 days.
The sandbox at sandbox-api.hibr.ai is free to use, runs full feature parity with production, and is pre-populated with sample UAE SMB data. You can read the API reference and try requests before reserving a beta seat. We believe gating the developer story behind a contact form is the fastest way to lose serious integration partners.
Create an invoice on a UAE customer with 5% VAT:
# Request curl https://api.hibr.ai/v1/invoices \ -H "Authorization: Bearer hibr_live_xxx" \ -H "Idempotency-Key: 9f8e7d6c-..." \ -H "Hibr-Version: 2026-10-01" \ -d '{ "customer_id": "cust_01HFQA...", "invoice_date": "2026-10-15", "currency": "AED", "lines": [ { "item_id": "item_01HFQA...", "description": "Consulting — October", "qty": "1", "unit_price": 500000, "vat_code": "VAT_STD_5" } ] }' # Response · 201 Created { "id": "inv_01HFQB...", "invoice_no": "INV-2026-001234", "status": "draft", "total_excl_vat": 500000, "total_vat": 25000, "total_incl_vat": 525000, "currency": "AED", "created_at": "2026-10-15T09:32:14Z", "links": { "self": "https://api.hibr.ai/v1/invoices/inv_01HFQB...", "pdf": "https://api.hibr.ai/v1/invoices/inv_01HFQB.../pdf", "e_invoice_xml": "https://api.hibr.ai/v1/invoices/inv_01HFQB.../pint-ae" } }
Note the amounts are in fils (AED minor units): 500,000 fils = 5,000.00. Note the response includes ready-to-fetch links for the PDF and the PINT-AE e-invoice XML. Note the vat_code input — semantic VAT classifications, not raw percentages, so a code change at FTA changes the engine, not your integration.
HIBR will publish first-party SDKs in the three languages most-used by UAE SMB integration teams:
@hibr/nodeTypeScript-first. Full type definitions. Promise-based with async iterator support for paginated resources. Available npm install @hibr/node at production launch.
hibr (PyPI)Sync + async clients. Pydantic models for request/response validation. Available pip install hibr at production launch.
hibr/hibr-phpPSR-7 / PSR-18 compliant. Works with Guzzle out of the box. Useful for Laravel + WordPress integrations. Available composer require hibr/hibr-php at launch.
Community-contributed SDKs in Go, Ruby, Java, .NET, Rust, and Elixir are encouraged. We will list them in a community section once the first version of the official SDKs stabilizes.
Two authentication models supported:
Full authentication details: /developers/api/
Resource catalog finalized. Endpoint shapes published in this developer documentation. RFC-style review window for community comment.
Sandbox at sandbox-api.hibr.ai accepts requests. Pre-populated with sample UAE SMB data. Free, no signup.
Node, Python, PHP SDKs published to package registries. Tagged alpha — API contract still tracking design freeze + customer feedback.
Production launch. api.hibr.ai accepts live requests. SDKs go GA. Version 2026-10-01 stable.
Machine-readable spec at https://api.hibr.ai/openapi.json. Compatible with OpenAPI Generator for community SDK generation.
Model Context Protocol server published. AI agents (Claude, GPT, others) can connect directly without intermediate API wrappers. First-class agent support.
Reserve a beta seat to get sandbox access in August 2026, three months before production launch. Beta participants help shape the final API contract.
Reserve founder slot →