One API for shipment,
customs, and settlement state.
Connect authorized carrier and customs systems, normalize their events, and evaluate cross-border settlement conditions.
No credit card required. The paid API is not yet available.
From observation to eligibility
Provider connection → authenticated observation → normalization → trade responsibilities → deterministic rules → HOLD, RELEASE_ELIGIBLE, REFUND_ELIGIBLE, or MANUAL_REVIEW.
Public reference data, authorized status, sandbox results, and simulations carry explicit source metadata. TradeShip does not hold or move funds.
Preview endpoints
| Endpoint under /api/v1/trial | Credits |
|---|---|
GET providers | 0 |
GET usage | 0 |
POST customs/context | 1 |
POST shipments/status | 1 |
POST customs/status | 1 |
POST simulate | 2 |
POST evaluate | 1 |
Defaults shown; the usage endpoint reports configured costs. Invalid inputs cost zero. Upstream/auth/quota failures are refunded. A provider-confirmed missing reference is charged.
Bring your authorized provider access
DHL connections use encrypted customer credentials. UPS uses delegated OAuth. FedEx uses customer registration when platform approval is available. HMRC offers a sandbox/production authorization path. Institutional systems such as EU ICS2, ABF, ICEGATE, TradeNet and NACCS require onboarding.
Provider credentials are encrypted at rest and never returned after save. Provider fees and quotas remain separate from TradeShip credits.
Download OpenAPIBuild beyond one region
World Bank supplies global historical context; Eurostat provides EU trade statistics; DBT exposes UK public datasets. These sources do not establish customs clearance or calculate duties. The directory shows unactivated providers and their exact access requirements.
Join the future paid API waitlist →Evaluating TradeShip for an integration?
Tell us what you use today. No account required.