Built API-first, so connecting Farexa isn't an afterthought.
{
"invoice": {
"number": "INV-2026-00042",
"tenant": "acme-retail",
"branch": "downtown",
"customer": { "id": "cus_1284", "name": "..." },
"lines": [{ "sku": "SKU-4471", "qty": 2, "total": 158.00 }],
"tax": { "scheme": "VAT-AE", "rate": 0.05 },
"status": "paid"
}
}Where Farexa connects
Grouped by the job the connection does, with an honest status on each - most of this is roadmap, and we say so.
Messaging & notifications
- WhatsAppRoadmap
Customer communication, invoice sharing, support updates, and campaign messaging.
- SMSRoadmap
Reminders, order and appointment updates alongside the platform's existing email notifications.
Payments & billing
- Payment gatewaysRoadmap
Payment collection and transaction references for POS sales, invoices, and subscriptions.
- ReconciliationRoadmap
Match gateway settlements back to the sales and invoice records that generated them.
Accounting & finance
- Structured exportsFoundation ready
Tax-aware sales, purchase, and expense records prepared for external accounting review.
- Number sequencesAvailable today
Consistent invoice, order, and document numbering an external ledger can rely on.
Analytics & reporting
- Excel & PDF exportAvailable today
Sales, inventory, purchase, and expense reports export directly for spreadsheets and BI tools.
- Audit trailAvailable today
Who changed what, and when, on every approval-worthy record - already written, not bolted on.
Delivery & e-commerce
- Delivery partnersRoadmap
Trip and driver context ready to hand off to a third-party delivery or logistics provider.
- Online storefrontsRoadmap
The same product catalog that already powers tenant websites, extended to external storefronts.
Business & partner systems
- Portals & partner toolsFoundation ready
Integration-ready direction for connected apps, customer portals, and partner systems.
- Industry-specific systemsExtensible
Sector tools - property, healthcare, manpower - that read from the same tenant record.
One API, not one per connection
Every app on Farexa - the web workspace, and the staff, employee and driver apps as they roll out - already runs on the same tenant-aware platform. A business integration doesn't get a special-cased shortcut around isolation, permissions or the audit trail; it gets the same rules everything else already follows.
One tenant boundary, enforced once
Every record already carries tenant and branch scope at the data-access layer, so a connected workflow inherits isolation instead of re-implementing it.
Role-aware by default
The same permission model that gates a cashier from a refund gates what an integration is allowed to read or write.
Every write is already audited
Create, update, approve and delete actions land in the audit trail automatically - a connected workflow's actions are traceable from day one.
Integration questions
Does Farexa have a public API today?
Not a public self-serve API yet. Every record already has a clean, tenant-scoped, permission-checked shape internally - that foundation is what a connected workflow is built on when we scope it with you.
Is WhatsApp or SMS messaging available now?
Not yet - both are on the roadmap. Notifications inside the platform (alerts, reminders, status updates) are already live; outbound WhatsApp and SMS channels are planned next.
Can I already export data to my accountant?
Yes. Sales, purchase, and expense reports export to Excel and PDF today, and every document follows a consistent numbering scheme, so an external accountant can work from clean exports now.
How do I request a specific integration?
Tell us the business system, the workflow it should support, and who's affected - see the integration playbook for the planning flow we use, or contact sales directly.
Have a specific system to connect?
Tell us the business system, the workflow, and who's affected - we'll scope a tenant-safe path to it.