Predictable REST + JSON
Clear resources, consistent JSON responses, and errors with stable codes your software can handle programmatically — no parsing of prose messages.
API-first for real
Issue, query and archive transport control documents from your TMS or ERP: REST + JSON, signed webhooks with retries and dead-letter, idempotency, and an unlimited sandbox to build without fear.
The sandbox never consumes credits.
- REST + JSON
- Signed webhooks with retries
- Dead-letter and replay
- Idempotent writes
- Sandbox with unlimited credits
What your team will find
The capabilities you would expect from a modern API, applied to Spain's transport control document.
Signed webhooks, with real retries
Every delivery is signed so you can verify its origin. If your endpoint fails, we retry with increasing back-off; if it keeps failing, the event sits in a dead-letter queue and you replay it with one click. Nothing is lost silently.
Unlimited sandbox
A test mode with unlimited credits: the same behaviour as production, without spending balance. Build, test and break whatever you need.
Idempotency
Write operations accept an idempotency key: after a timeout or a dropped connection, retry the same request without any risk of issuing the document twice.
Scoped API keys
Per-account keys with permissions limited to what each integration needs, and immediate revocation from the panel.
OpenAPI and Postman for approved accounts
The full specification and the Postman collection ship with approved developer access: you work against the exact API contract, not screenshots from a blog post.
The whole flow, in three steps
An illustrative example of the typical integration: create the document, activate it, react to the webhook. Endpoints and fields shown are examples; the real contract ships with developer access.
1 · Create the document from your software
curl -X POST https://api.example.com/v1/transport-docs \
-H "Authorization: Bearer sk_live_..." \
-H "Idempotency-Key: 4c9d1e0a-7b2f-4e11-a3c8-..." \
-d '{
"type": "DECA",
"shipper": { "name": "Cargas Ibero SL", "taxId": "B00000000" },
"carrier": { "name": "Transportes Vega SL", "taxId": "B11111111" },
"origin": { "city": "Madrid" },
"destination": { "city": "Valencia" },
"vehicle": { "plate": "0000AAA" },
"goods": "24 pallets - 8,400 kg"
}'
HTTP/1.1 201 Created
{ "id": "doc_7f3k9q", "status": "draft", ... }2 · Activate it when the transport starts
curl -X POST https://api.example.com/v1/transport-docs/doc_7f3k9q/activate \
-H "Authorization: Bearer sk_live_..."
HTTP/1.1 200 OK
{
"id": "doc_7f3k9q",
"status": "active",
"inspection": { "url": "https://inspection.example.com/i/Xy4Zw9" }
}3 · Receive the webhook on your endpoint
POST https://tms.example.com/webhooks/transport
X-Signature: sha256=9b1c47e0a2...
{
"event": "document.activated",
"documentId": "doc_7f3k9q",
"occurredAt": "2026-07-06T10:24:31Z",
"attempt": 1
}Verify the signature, answer 2xx and you are done. If you don't answer, we retry.
How to get access
The sandbox is instant; the full specification is delivered after manual approval.
- 1
Create your free account
Self-service sign-up, no card. From minute one you can issue test documents in sandbox mode.
- 2
Request developer access
From the panel, tell us what you want to integrate. We review every request by hand: we like knowing who builds on the platform.
- 3
Receive the full specification
With approval you get the full OpenAPI and the Postman collection, and your account is enabled to integrate in production.
The pattern TMS vendors follow
If you build software for carriers or shippers, this is the model that fits.
A partner account issues documents on behalf of its end customers, accrediting on each document which customer it belongs to. Your users keep working in your TMS as always: your software creates and activates documents through the API, receives a webhook for every status change, and shows the QR and the PDF wherever suits you.
We provide compliant issuing, legal archiving and the evidence trail; you keep the customer relationship and your product. Pricing is by volume andcustom.
We are integrating the platform with the first TMS vendors. This spot is reserved for the testimonial of the first one in production — want it to be yours?
Developer questions
The usual doubts before writing the first line.
Can I build without paying?
Yes. Create a free account and work in sandbox mode: the same flow as production, with unlimited test credits. You only spend real credits when you issue real documents.
Do you publish the full API specification?
Yes, but not in the open: the full OpenAPI and the Postman collection are delivered to accounts with approved developer access. That keeps the API contract in the hands of people who actually integrate. Requesting access is free and done from the panel.
What happens if my webhook endpoint goes down?
Nothing is lost. Every failed delivery is retried automatically with increasing back-off; if it keeps failing, the event is held in a dead-letter queue and you can replay it once your endpoint is back.
Can I issue documents on behalf of my customers?
Yes: that is the partner pattern built for TMS and ERP vendors. Your account issues documents accrediting the end customer on each one, and your customers never need to touch our platform. More on the partner model.
89daysuntil 5 October 2026
Start with the sandbox
Create your free account, issue test documents today and request developer access from the panel.