Does this record already exist?
It retains the external identifier and the system that created it. Submit the same information should not create another job.
Connect once. Keep the meaning.
The API moves data. A good contract keeps where they come from, what they mean and what can be done with them. That's the starting point for integrating Drometra.
Drometra / data interfaceExample
The connection starts on the contract.
GET / /observations01 — 07
{
"asset_id": "veh_demo",
"kind": "position",
"origin": { "channel": "gateway" },
"occurred_at": "2026-09-26T09:00:00Z",
"received_at": "2026-09-26T09:00:03Z"
}Origin and reception are different times. Explanatory example; does not send requests.
Four questions before writing the first connector
A useful integration also resolves the second synchronization, the corrected data and the supplier that takes to respond.
Who can change this data?
Define the master by domain and, when necessary, by field. Catalogue, stock, work and evidence do not need to belong to the same system.
When did it happen and when did it come?
Separate time of origin and reception. A late update should not look like an event that just happened.
What if the connection is cut?
According cursor, deduplication, unknown states and reconciliation avoids turning a reattempt into a second effect.
Less glue, more logic of your business.
The client layer should help with types, authentication and error treatment. The adapter translates the source system without bringing its particularities to the rest of Drometra.
- An explicit mapping for each field and its unit.
- Initial reading and updates with a recoverable advance position.
- Reported capacities: what the supplier does not offer is not simulated.
Language, bookstores and access to the environment are agreed according to the connector. The reference does not mean that there is a public package for each language.
One adapter, three responsibilities
Entrada
Read the origin with your permissions and limits.
Translation
Map fields without erasing provenance.
Resultado
Record what was processed and what needs review.
The order leaves the ERP. The result returns with its reference.
Receive order
The ERP retains catalogue and order. Its identifier, address, quantities and conditions are related to the operational work.
Resolve on the ground
Drometra conserves visit, attempt, reception and evidence. A partial delivery maintains amounts and next action.
Return the result
The result allowed by the contract, with identifiers and version, is reported. A shipping failure remains to be reconciled, without duplicating the effect.
It brings a flow, not a list of logos.
An anonymous sample and a frequent exception allow you to design a contract that really covers your operation.
- System and version; documentation of the API you have access to.
- Fields needed and who keeps each one.
- Anonymous example of input, change and expected result.
- Permissions, frequency, volume and way to recover a failure.
Preguntas frecuentes
Let's build a connection with purpose
Show us the system, the work that must be crossed and the exception that you are hard to solve today.