Documentation
Cargofollow is infrastructure for electronic freight documents in the EU. One POST /v1/shipments
gives you a consignment note with a hash chain, signable links, documents and webhooks — plus the
eFTI dataset in the shape Regulation (EU) 2020/1056 prescribes.
QuickstartFrom a key to a signed, delivered shipment in the sandbox.
API referenceEvery route with examples, callable against the sandbox.
Error codesEvery stable code the API returns in problem+json.
SDKsTypeScript today, .NET next.
How the API fits together
Section titled “How the API fits together”- One resource at the centre. A
shipmentbundles parties, goods, documents, signatures and events. Everything hangs off it. - Issuing freezes it.
POST /v1/shipments/{id}/issuelocks the consignment note fields and adds the first link in the hash chain. After that, every change is a new, verifiable version. - Errors are
application/problem+json. Every error carries a stablecode, arequest_idand, on validation, anerrorsarray per field. See Error codes. - Test and live are separate. Your key prefix (
sk_test_orsk_live_) decides the mode; data from the two modes never mixes.
Base URLs
Section titled “Base URLs”| Environment | API | Status |
|---|---|---|
| Sandbox | https://api.eftisandbox.app |
Available |
| Production | https://api.cargofollow.com |
In preparation |