The same API the console and Dromivia use, with 146 routes for the fleet, orders, routes, field work, reports and integrations, and signed webhooks so your system finds out what happens.
In productionversion 0.4.0api.drometra.com
{
"actorId": "0b6f8c2e-4a1d-4e5b-9c3f-2d7e8a9b1c4d",
"tenantId": "0b6f8c2e-4a1d-4e5b-9c3f-2d7e8a9b1c4d",
"role": "viewer"
}1
You sign in as a person in your company, with the role what you're doing needs: reader, operator or administrator.
2
It's issued by auth.drometra.com when you sign in. For a system to connect on its own, write to us: those credentials are in development.
3
Request your context: who you are, in which company and with which role. If it responds, you already have everything the other routes require.
curl "https://api.drometra.com/v1/context" \
-H "Authorization: Bearer $DROMETRA_TOKEN" \
-H "x-tenant-id: $DROMETRA_TENANT"Writes also require idempotency-key. All of that, errors and pagination are in Concepts.
The specification is the same one the API runs on. You can use it to generate a client in your language or import it into your testing tool.