Overview
“Can you integrate with X?” is the question every ERP vendor is asked, and the honest answer usually depends less on the ERP than on the other system.
Nama ERP’s position is deliberate: it is open by default. A fully documented REST API, following the OpenAPI 3.0 specification, covers CRUD operations on every entity in the system — and it is available to every customer at no additional cost. Where an integration does carry a cost, that cost almost always originates on the other side.
Features
Ask the direction first
Most integration conversations go wrong because nobody establishes which way the data flows. There are four cases, and they are not equally difficult:
| Direction | Who must provide the API |
|---|---|
| Another system reads from Nama ERP | Nama ERP — already available |
| Another system writes to Nama ERP | Nama ERP — already available |
| Nama ERP writes to another system | The other system |
| Nama ERP reads from another system | The other system, or its database |
Both directions that depend on us are already solved and included. Real projects usually need more than one at once — pushing items to a web shop and pulling its orders back — so it is worth naming each direction before anyone quotes.
An API browser, not just a specification
The system ships an interactive API browser served from your own installation, so developers can explore and test the endpoints against real data rather than reading a PDF. Entity APIs are listed with their Arabic and English names, alongside special-purpose APIs for specific integrations such as attendance-machine synchronisation.
Integrator endpoints — inbound data with logic attached
Beyond straight CRUD, an integrator endpoint gives an external system an address to call, and hands what arrives to an Entity Flow. That means inbound data is not merely stored — it is validated, transformed and used to generate whatever documents should follow, all in configuration.
Ready-made links
Some integrations are already built:
- Attendance machines, by two supported methods, feeding time and attendance directly.
- E-commerce, including reading orders, returns and abandoned carts, and pushing quantities back — see e-commerce integration.
- Invoice Retriever, which sends customers and suppliers a link that generates and serves their documents on demand.
- E-invoicing with the Egyptian, Saudi and UAE authorities — covered by their own pages.
Before you ask for a quote
The documentation includes the framework our own sales and implementation teams use: the four directions, which scenarios are free out of the box, which need development, and the questions worth asking before a proposal is prepared. It is published openly because a customer who arrives with those answers gets a better and faster one.
Read the integration documentation and the REST API guide.
