tenantReference on every document
Each document carries your end customer's reference: usage broken down per customer, per-customer filtering and zero mixing between portfolios. One integration, your whole installed base.
Integrate once. Issue for all your customers.
If you sell a TMS, a vertical ERP or logistics software, 5 October 2026 is your date too: your customers will expect Spain's DeCA inside your product. Our multi-tenant API makes it a single integration — and the same engine issues the European eCMR.
Sandbox included. Start with 10 free documents.
Multi-tenant by design, not an afterthought
The API assumes from the start that one software vendor issues on behalf of many end customers.
The legal engine is our job
Art. 6 validation, a QR-equipped PDF meeting the technical requirements, archiving and evidence: your software sends the transport data, we answer for compliance.
Your references, respected
Documents accept your own references (file, order, trip) so your TMS and our records speak the same language.
Integration reliability you can audit
The three things a developer asks first, answered by design.
Webhooks with retries
Every event (activation, changes, inspection, completion) reaches your endpoint with automatic retries, a dead-letter queue and manual redelivery from the panel. If your server goes down, you lose nothing.
See details
Real idempotency
Idempotency keys on write operations: retry without fear of duplicating documents or spending credits twice.
See details
Sandbox and published limits
A complete test environment and documented rate limits. No production surprises, no "we'll see" during due diligence.
See details
Running technical due diligence? SLA, DPA and service status are published onthe trust page →
The partner path, in three steps
No committees, no 80-page PDFs: an integration measured in days.
- 1
Tell us your case
What software you sell, how many customers run domestic Spanish transport and what volume you expect. We reply with the volume pricing model.
- 2
Get the spec and the sandbox
We approve your access to the full specification (OpenAPI + Postman) and you build against the sandbox with our support.
- 3
Go live with your customers
Activate end customers with their tenantReference and bill however you prefer. We answer for compliance and for inspection availability.
RoadmapWhite-label for partners
Today: the PDF supports the issuing company's logo and your references travel with every document. On the roadmap: a fully branded experience. We share real dates when we talk — no brochure promises.
Questions from integrators
How does billing work for a software vendor with many end customers?
Your partner account issues with an end-customer identifier (tenantReference) on every document: usage is broken down per customer and you decide how to pass it on. Pricing is on aggregate volume, sized case by case.
Is there a test environment?
Yes: a sandbox with the full workflow so you can build and test your integration without spending credits or touching live data. Your customers can also use test mode when switching the integration on.
Can I offer it under my own brand (white-label)?
The PDF already supports the issuing company’s logo, and full white-label is on our partner roadmap. Tell us your case and we will give you honest dates — we do not sell what does not exist yet.
Why don’t you publish the full API specification?
The complete technical documentation (OpenAPI + Postman collection) is released to registered accounts with approved access: it lets us support every integration properly and protect our partners' work. The overview lives on the developers page.
89daysuntil 5 October 2026
Your customers will ask for the DeCA inside your software
Get ahead of 5 October: request access to the full specification and the sandbox.