API and ERP integration
We connect the software your company already uses, so data moves between systems without manual copying: ERP, invoicing software, online shops, GPS systems and ANAF systems.
What an API integration means
An API integration links two programs so data passes from one to the other by itself, with no manual copying: orders from the online shop into invoicing, GPS positions into the transport app, data sent to ANAF.
We build the integration where no ready-made module exists, or where the existing one does not do everything needed. Every transfer is tracked, so an error is seen and retried, not lost.
When you need this
- The same orders or invoices are copied from one program to another.
- Your software has no ready-made link to the system you need.
- The existing link doesn't do everything you need.
- Reporting to ANAF is done by hand.
What we build
API integrations
Direct links between applications, with the data checked on every transfer.
ANAF systems
Data sent to ANAF straight from your company's applications, like the RO e-Transport positions in GPS'CU.
GPS and telematics
Data from the GPS systems your company already has, brought into your applications, as EvitaAmenda does.
Monitored sync
Data syncs automatically, and a failed transfer is flagged at once.
How we work
Each stage in detail- Analysis
- Prototype
- Development
- Launch and support
What affects cost and time
The price of a project is, roughly, the working time. These make it larger or smaller.
- How well the other software is documented
- An API with clear documentation and a test environment goes quickly; one without them takes trials and talks with the vendor.
- Which way the data flows
- One way is simpler than both ways, where conflicts must be resolved too.
- Volume and frequency
- A few records a day and positions every few seconds need different builds.
- Security
- Certificates, access keys and the transfer log are part of the work.
What we work with
- Integrations
- REST · OpenAPI (Swagger) · TCP
- Security
- API keys · Certificates (mutual TLS)
- Server
- NestJS · Node.js · TypeScript
- Data
- PostgreSQL
Frequently asked questions
What do you need to start?
The names of the programs, which data must move and in which direction. If a program has API documentation, send it to us and we review it.
What if a program has no API?
We look for another safe route, such as automatic file export and import, agreed with the program's vendor.
Does the integration keep working after software updates?
We monitor it and adapt it as part of maintenance when a vendor changes its API.
Our software already has an integration module. Do we still need this?
If the module does everything you need, no. We build the integration when there is none or when the existing one does not cover your cases.
Can you also offer an API for our partners?
Yes. GPS'CU, for example, has a public API with access keys and documentation, for companies that want the data in their own software.
Related services
Have an idea? Let's talk.
Tell us what you want to build. We'll come back with the right questions, then a quote.