OpenAPI 3.1
The released integration API is described by a version-controlled OpenAPI 3.1 document and checked against the application route contract.
Download the API contractStandards and interoperability
Review the interface standards implemented today, the GS1 models informing the product, and the logistics interoperability capabilities still planned.
Current posture
The status beside each standard is part of the claim. It should not be read as a general certification of RouteHut or of an operator using it.
The released integration API is described by a version-controlled OpenAPI 3.1 document and checked against the application route contract.
Download the API contractWebhook deliveries use the Standard Webhooks ID, timestamp and signature headers with the versioned HMAC-SHA256 signing scheme.
Review webhook verificationAppend-only scan and custody records retain the object, time, place and operational context of a movement. RouteHut does not yet expose or ingest EPCIS 2.0 documents.
Inspect the custody workflowOptional SSCC validation and standards-based label generation are planned for operators whose trading process uses GS1 logistic units. Current RouteHut parcel numbers are tenant-specific identifiers.
Review parcel identification scopeGLN support is planned as an optional external identity for parties, hubs and service points. RouteHut does not currently allocate or validate GLNs.
Review service-point scopeClaims boundary
GS1 identifiers must come from the operator or another authorised party using a valid GS1 Company Prefix. RouteHut does not issue GS1 identifiers.
A platform capability does not make every tenant workflow standards-conformant. Identifier allocation, label content, scanners, master data and trading-partner agreements must be configured and verified together.
RouteHut does not currently claim ISO certification or universal compliance for dangerous goods, pharmaceuticals, customs, postal services or any jurisdiction-specific transport regime.
Primary references
These links point to the standards bodies themselves. They are references for implementation and verification, not endorsements of RouteHut.