Shipment API
Two capability profiles share access planning, support, and onboarding controls. Customer differences belong in approved mappings, not in a public API fork.
Capability profiles
Use the operating model to choose a fit. Entitlement is agreed during onboarding; one profile does not automatically include the other.
Shipment Visibility
Private previewTrack shipment state and receive terminal and rail visibility data while keeping the customer shipment system of record.
- Who it is for
- Teams that retain shipment ownership and need EDRAY visibility data.
- You provide
- Shipment identifiers
- Equipment identifiers
- Locations needed for matching
- EDRAY provides
- Create and reconcile the visibility record
- Normalize ocean terminal and rail visibility data
- Return governed visibility updates through the approved integration
- You receive
- Ocean terminal visibility data
- Rail visibility data
- Outbound integration
- Terminal and rail visibility data
- Availability
- Available through EDRAY-managed onboarding in private preview.
Managed Shipment Creation
PlannedCreate and manage drayage shipments in EDRAY from a richer customer data set.
- Who it is for
- Teams that want EDRAY to create and manage the drayage shipment lifecycle.
- You provide
- Richer shipment, leg, purchase-order, and item data
- Routing and location context
- Equipment and purchase-order context
- EDRAY provides
- Create the managed shipment
- Run EDRAY managed drayage workflows
- Reconcile lifecycle changes
- You receive
- EDRAY-managed drayage execution
- Outbound integration
- Not currently offered
- Availability
- Planned capability. The approved request-body preview is public; no outbound customer integration is currently offered.
Shared controls
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.