Integrations
Fits the systems you already run
Plomba speaks the formats the container industry already uses. Read and react to sealed handovers over a REST API and signed webhooks, send CODECO gate messages, and hand out the EIR as a PDF.
REST API
Everything the app does, over HTTPS
The phone app uses the same JSON API you integrate with: containers, handovers, photos, marks, sealing and history. Every installation describes it in OpenAPI at /api/openapi.json, so you can generate a client in your own language.
curl https://plomba.example.com/api/openapi.json
| Request | What it does |
|---|---|
GET /api/containers?owner={code} | The fleet of an owner code, most recently handed over first |
GET /api/containers/{number} | A container's sealed history and damage passport, with the hash chain verified |
GET /api/handovers?vehicle={plate} | Find handovers by truck, wagon, container, status or place, page by page |
POST /api/handovers | Start a handover |
GET /api/handovers/{id} | A handover with its photos and marks |
GET /api/handovers/{id}/codeco | The CODECO message for a sealed handover |
POST /api/handovers/{id}/claim | Draft a claim for new damage, verified against the sealed records |
Signed webhooks
Hear about each handover as it is sealed
Give the installation your HTTPS endpoint and Plomba posts handover.started and handover.sealed events to it. The sealed event carries the marks and, for each damage, the last handover that photographed the spot clean, so a claims, fleet or transport system can act without asking again. Other systems call the API with their own token.
Plomba-Signature: t=<unix>,v1=<hex>
tis when the delivery was signed, as Unix time. Reject old deliveries so a captured one can't be replayed.v1is the HMAC-SHA256, in hex, of<t>.<raw body>, keyed with the webhook secret. Check it, in constant time, before you parse the body.- Any 2xx answer means received. Anything else is retried after 1 s, 10 s and 60 s, with the same
Plomba-Deliveryid, so duplicates are easy to skip. - The claims desk in
examples/verifies deliveries this way, and its tests use real signed deliveries.
EDIFACT CODECO
Gate messages your EDI already reads
Every sealed handover can be sent as a CODECO, the container gate-in and gate-out report shipping lines and operators already exchange.
- Directory D.95B in the SMDG 1.6 profile: BGM 34 for gate-in, 36 for gate-out.
- Up to nine damages with ISO 9897 location, damage and component codes (DAM and COD).
- The sealed record's SHA-256 in an FTX segment, so the message points to the tamper-evident record.
- The road or rail leg that brought or collected the container (TDT).
UNA:+.? '
UNB+UNOC:3+PLOMBA+CARRIER+261103:1330+AE30122521AA75'
UNH+AE30122521AA75+CODECO:D:95B:UN:SMDG16'
BGM+36+PLBU4000043-4+9'
NAD+MS+PLOMBA'
EQD+CN+PLBU4000043+42G1:102:5'
RFF+SQ:1'
DTM+7:202611031330:203'
LOC+165+:::LODZ INLAND TERMINAL'
FTX+AAI+++PLOMBA RECORD SHA-256:AE30122521AA75F00DC5A04115FF5A9B638829BFF57C849633951EE4B159376E'
DAM+1+CO+LT78'
COD+PAA'
DAM+1+DT+LB3N'
COD+PAA'
TDT+1+EL4K217+3'
CNT+16:1'
UNT+15+AE30122521AA75'
UNZ+1+AE30122521AA75'
codeco.ts).EIR as PDF
The receipt both parties keep
Every sealed handover has an equipment interchange receipt: the parties, the place and time, the photos of each face and every damage with its code. Print it, or save it as a PDF.
- Each damage says where it was first recorded or, if it is new, which handover last photographed the spot clean.
- The sealed record's hash is on the receipt, so anyone can check it against the history.
Equipment interchange receipt
- Container
PLBU 400004 3· 42G1- Handover
- #4 Gate out · Łódź inland terminal
- Date
- 3 Nov 2026
- Transport
- Truck EL 4K217
| Code | Damage | History |
|---|---|---|
LT78 CO | Corroded | First recorded at #1 |
LB3N DT | Dent | New. Spot last photographed clean at #2 |
Record SHA-256 ae30122521aa75f00dc5a04115ff5a9b638829bff57c849633951ee4b159376e
Examples
Runnable examples, one per party
Small programs in the repository's examples/ folder that show an integration from start to finish.
-
Shipping lines and shipowners
examples/shipping-line-claims-deskA claims desk that checks each signed delivery and opens a claim for damage that appeared on a leg, addressed to whoever had the container. -
Intermodal and rail operators
examples/rail-operator-train-arrivalTurns a train's wagon list into gate-in handovers before the train arrives. -
Trucking companies
examples/trucking-driver-receiptFinds a truck's sealed handover and prints the driver's receipt, with the record's hash checked. -
Container owners and leasing companies
examples/leasing-fleet-conditionA fleet condition report by owner code, and the damage that appeared between on-hire and off-hire.
Standards
Codes the industry already uses
Plomba records in the standards your partners already exchange, so its records fit the systems you run.
- ISO 6346
- Container numbers with their check digit, and size and type codes
- ISO 9897 (CEDEX)
- Damage location, damage and component codes
- EDIFACT CODECO D.95B
- Gate-in and gate-out reports, in the SMDG 1.6 profile
- UIC wagon numbers
- Twelve digits with a self-check digit, checked as they are typed
Need EDI or TOS connections built for you?
Connections to your EDI partners and terminal operating system are part of Plomba Enterprise.