APIs for governed freight information
We build the systems that move freight information. Public pages explain families and operating models. Credentials, entitlements, and complete contracts stay in the secure APIM portal after EDRAY-led onboarding.
Shared integration foundation
Approved shipment scope
Confirm permitted shipment scope and identifier mappings during onboarding. Use only the IDs approved for your integration.
APIM access
Production shipment creation requires an APIM subscription key. Obtain access details for the agreed integration profile from EDRAY.
Request records and retries
Retain request references and response details for support. Confirm retry and duplicate-handling behavior for your integration during onboarding.
Asynchronous processing
Submitting a request does not confirm completed shipment creation. Agree on how processing outcomes are reported.
Recovery controls
Agree on failure reporting, retry, and recovery expectations for your integration during onboarding.
Separate approval
Access is enabled after the agreed approval process. Preview access does not activate an integration.
EDRAY-led onboarding
Qualification, certification, and production approval are managed with EDRAY rather than opened as public signup.
API families
Shipment API is the current public family. Other integration work stays inside approved customer programs until a family is ready to publish.
Shipment API
Compare capability profilesOne product foundation with two customer-entitled profiles. The profiles differ by operating model and the data a customer supplies, not by a public API fork.