Transport control document (DeCA) and transport weight

From 5 October 2026 the administrative control document of Spanish public road freight transport must be digital. The public API now issues it: a PDF per version, served from a permanent public URL whose QR code travels with the driver, with the history the inspection needs. Everything is additive; no existing field changes meaning. See the Transport control document guide.

New transport_documents resource

New scopes: transport_documents:read, transport_documents:write, transport_documents:delete and transport_documents:transition, also grantable through OAuth. The PDF of each version enforces pdfs:read; the proof of issuance, transport_documents:read, because it contains the issuance evidence. The transport_documents module requires delivery_notes.

MCP, events and errors

• 15 MCP tools, one per operation except the QR code and the proof of issuance, which stay binary REST downloads. search_transport_documents takes the same q and sort as the REST list, and create_transport_document does not take id. See the tool catalog.
• 10 events: transport_document.created, .updated, .issued, .modified, .closed (with close_mode manual or automatic), .reopened, .cancelled, .superseded, .email_sent and .email_failed. While a document is a draft, its parties follow changes to the linked contact and to your company data, and each refresh that changes something publishes .updated. See Events.
• 24 error codes: the 22 of the new «Transport Documents» category, from transport_document_not_issuable (with error.details.missing) to transport_document_version_limit_reached, transport_document_pdf_too_large and transport_document_version_not_found (404 for a ?version=N the PDF does not have), plus invalid_gross_weight (also on the goods lines of a document) and gross_weight_not_allowed in Products. See the error catalog.

Limits and identifiers

• A document holds at most 50 versions, the last one reserved for cancelling or superseding it; once it has 49, modify returns 422 transport_document_version_limit_reached.
• Each version is a PDF of up to 5 MB (5,000,000 bytes). Issuing, modifying, cancelling and superseding return 422 transport_document_pdf_too_large without saving anything when the PDF would be larger.
• The server generates the id of a document. shipments[].id is optional: on create, one already in use returns 422 on shipments.N.id; on update and modify, it only identifies a shipment of that document. A concurrent write that collides on an identifier returns 409 resource_conflict and can be retried. UUIDs are normalised to lower case.
• On create, a shipment that omits origin takes your default loading place or your registered address; an explicit "origin": null leaves it without origin.
• The public URL is limited per token and network prefix (60 per minute by default) and per token (600 per minute by default), never by IP alone; unknown tokens count per network prefix. The public PDF does not show who made each version.

Gross transport weight in the catalog and on delivery notes

• Products, variants and fixed presentations accept gross_weight_kg on create and update and publish it on read: kg per base unit on products and variants and per commercial unit on presentations. Omitting it on update keeps the current value and null clears it. Services, mass base units (KGM, GRM) and variable_measure presentations reject it with gross_weight_not_allowed.
• Delivery note lines freeze their weight when created or edited in draft and publish it as gross_weight_kg; the delivery note adds total_gross_weight_kg and lines_without_weight_count.
• Series accept the new type transport_document (default code DC); its series is created on the first issue. GET /v1/series/stats counts it.