Developer integration

A stable contract around changing compliance rules.

The intended API accepts a controlled shipment record and scoped context, then returns rule results with ownership and evidence. Exact interfaces are defined and tested per pilot.

Example contract

Preflight is not submission.

Conceptual request

POST /v1/preflight
{
  "profile": "efti-eu",
  "shipment": {},
  "context": {
    "origin_country": "PL",
    "destination_country": "DE",
    "mode": "road"
  }
}

Conceptual response

{
  "status": "blocked",
  "profile_version": "example-version",
  "issues": [{
    "field": "consignee.identifier",
    "reason": "missing",
    "owner": "erp"
  }],
  "evidence": []
}
Honest capability labels

Know what can be demonstrated.

PUBLIC DEMO

Local assessment

The browser tools on this site; no authority connectivity.

PILOT

Scoped integration

Canonical mapping, validation fixtures and evidence in a defined customer project; availability is negotiated.

PLANNED

Authority-dependent paths

Live Gate, provider submission and certified platform claims require specific interfaces, agreements and testing.

Start with one workflow

Turn an integration question into a testable scope.

Map the data, name the owner, define the evidence and decide what to test before implementation.

Scope an assessment