Ellipse Gradient for Header

C.H. Robinson Integration Guide

Connect C.H. Robinson Navisphere transportation APIs with enterprise systems for rates, shipment booking, load management, and tracking synchronization.

C.H. Robinson integration options at a glance

C.H. Robinson’s Navisphere platform primarily integrates through REST APIs for transportation rates, shipment booking, load management, carrier information, and tracking. Selected accounts or API products may also support webhook-style notifications for shipment or load events, although coverage must be confirmed for each implementation. OAuth 2.0 application credentials and bearer tokens provide the documented authentication model, with separate sandbox and production configuration where available. Martini can consume these APIs, expose endpoints for callbacks, schedule incremental synchronization workflows, map logistics payloads, and apply validation, idempotency, retry, and reconciliation rules. Bulk APIs, general attachment APIs, GraphQL, SOAP, and direct database access are not confirmed.

Integration pointSupported by C.H. Robinson?Common use casesHow Martini supports it
REST APIsYesNavisphere REST APIs support rate and quote requests, shipment booking, load and shipment retrieval, supported updates, tracking, and selected reference data operations.Martini can consume the REST endpoints from workflows, map JSON payloads, apply business rules, and expose internal APIs around the resulting integration process.
Webhooks / outbound callbacksLimitedSelected shipment or load lifecycle events may be delivered through webhook-style notifications, subject to the API product and C.H. Robinson account configuration.Martini can expose an API endpoint to receive callbacks, validate and transform events, route them downstream, and use polling reconciliation for uncovered events.
AuthenticationYesNavisphere uses application registration and OAuth 2.0 access tokens supplied as bearer tokens in the HTTP Authorization header, with permissions or scopes where applicable.Martini can store client credentials in secrets or environment configuration, acquire or reacquire tokens, and keep sandbox and production settings separate.
Scheduled synchronizationYesWhen callbacks are unavailable or incomplete, integrations can retrieve recently changed loads or shipments using supported date, status, or last-modified filters.Martini can schedule workflows, persist watermarks, use overlap windows, paginate results, and reconcile missed or corrected updates.
Bulk / asynchronous / batch APIsNot confirmedPublic documentation reviewed did not confirm a generally available bulk or asynchronous Navisphere API. High-volume options should be confirmed for the assigned API product.Martini can orchestrate bounded, paginated REST calls, but a vendor bulk or asynchronous capability should not be assumed.
File / attachment APIsNot confirmedA general public file or attachment API was not confirmed. Bills of lading, proof of delivery, invoices, or other documents may require a separate capability or exchange channel.Martini can coordinate a confirmed file or document endpoint if provided, but should not assume that Navisphere attachments are available through the public API.
EDI and enterprise messagingLimitedEDI and transportation-industry messaging may be available for particular customers or products, but no universal public interface was confirmed in the reviewed Navisphere documentation.Martini can orchestrate approved exchange mechanisms when their specifications and endpoints are provided, while the C.H. Robinson onboarding team confirms transaction sets and responsibilities.
Database / analytics accessNoDirect database access to C.H. Robinson systems is not an expected integration method.Martini should use Navisphere APIs or other approved vendor data-exchange mechanisms rather than attempting a direct database connection.

How C.H. Robinson exposes data and business events

C.H. Robinson REST APIs

Navisphere REST APIs are the primary confirmed integration mechanism. Depending on the assigned API product and permissions, they support transportation rates, shipment booking, load and shipment retrieval, supported updates, tracking, and selected reference data operations.

Martini implementation pattern

Martini workflows authenticate with OAuth 2.0, call the required REST resources, validate responses, map shipments, loads, stops, rates, carriers, and tracking events, and write results to downstream systems. Reusable Martini APIs can provide a controlled internal façade for booking or status operations.

Implementation sequence

Acquire or reuse an OAuth 2.0 access token
Receive a booking, rate, or synchronization request
Call the applicable Navisphere REST resource
Validate the response and classify errors
Map the payload to the canonical logistics model
Write the result to the target system and persist correlation state

Webhook-style notifications

C.H. Robinson may provide event-oriented shipment or transportation updates for selected lifecycle events. Availability and coverage depend on the API product and customer configuration, so callbacks should not be assumed for every event.

Martini implementation pattern

Martini exposes a secured API endpoint for enabled callbacks, validates the request and event identity, transforms the notification, and routes it to operational or customer-facing systems. A scheduled reconciliation workflow fills gaps where required events are not delivered through callbacks.

Implementation sequence

Receive the callback for an enabled event
Validate authentication, payload structure, and event identity
Deduplicate the event using the supplied identifier or correlation key
Retrieve the current shipment or load when the notification is incomplete
Map the event to the internal status model
Route the update and record processing outcome

Scheduled status synchronization

Scheduled retrieval is the fallback or reconciliation mechanism when callback coverage is unavailable or incomplete. The workflow can query recently modified loads or shipments using filters supported by the assigned Navisphere API.

Martini implementation pattern

Martini schedules a workflow that reads a durable watermark, applies an overlap window, retrieves pages of changed resources, maps each result, and updates target systems. The workflow advances the watermark only after successful processing and records failures for retry or review.

Implementation sequence

Read the last successful synchronization watermark
Apply an overlap window and supported API filters
Retrieve and paginate recently changed loads or shipments
Map statuses, stops, tracking events, and identifiers
Upsert downstream records using idempotency keys
Advance the watermark and record reconciliation metrics

Common C.H. Robinson integration patterns

Pattern 1: Book shipments from an ERP

When to use this pattern

Use this pattern when SAP S/4HANA, NetSuite, or another internal system needs to request a rate or book a shipment with C.H. Robinson. It protects against duplicate bookings when the source retries after a timeout.

Integration direction
SAP S/4HANA
Martini
C.H. Robinson
Example Mapping
C.H. Robinson FieldCanonical FieldTarget Field
sourceShipmentIdshipment.sourceIdShipment reference
origin and destination stopsshipment.stopsStops
equipment or service requirementsshipment.transportRequirementsShipment requirements
quote or rate identifiershipment.rateIdQuote or rate identifier
Martini implementation pattern

Martini receives the request through a workflow or API, validates required stops and shipment attributes, checks the source-system idempotency key, requests a rate or creates the supported shipment resource, and returns the C.H. Robinson identifier and status. Transient failures are retried with bounded backoff; ambiguous outcomes are reconciled before resubmission.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • idempotency
  • error handling

Pattern 2: Synchronize loads and shipments to enterprise systems

When to use this pattern

Use this pattern to keep an ERP, TMS, visibility platform, or customer application aligned with recently changed C.H. Robinson loads and shipments when callback coverage is unavailable or incomplete.

Integration direction
C.H. Robinson
Martini
Oracle Transportation Management
Example Mapping
C.H. Robinson FieldCanonical FieldTarget Field
loadIdtransportation.externalIdLoad reference
shipment statustransportation.lifecycleStatusShipment status
stopstransportation.milestonesPickup and delivery milestones
carrier identifiertransportation.carrierIdCarrier reference
Martini implementation pattern

A scheduled Martini workflow reads a persisted last-modified watermark, applies an overlap period, retrieves paginated results, maps vendor statuses and stops, and upserts downstream objects. It records processed identifiers, retries transient API failures, and periodically performs a broader reconciliation to detect missed updates.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination
  • data mapping
  • state persistence
  • retry handling

Pattern 3: Route tracking events to operations

When to use this pattern

Use this pattern when the account supports selected C.H. Robinson callbacks and operations teams need near-real-time tracking or exception handling in Salesforce, ServiceNow, or a visibility platform.

Integration direction
C.H. Robinson
Martini
ServiceNow
Example Mapping
C.H. Robinson FieldCanonical FieldTarget Field
event identifiertrackingEvent.externalIdEvent correlation key
load or shipment identifiertrackingEvent.transportationIdShipment or load reference
event status and milestonetrackingEvent.lifecycleStatusTask or case status
event location and timestamptrackingEvent.locationAndTimeMilestone details
Martini implementation pattern

Martini receives the callback through an exposed API, validates and deduplicates it, retrieves the current resource when necessary, maps the event to the target lifecycle, and creates or updates operational work. Events outside callback coverage are recovered by scheduled reconciliation, while invalid payloads are routed to an exception workflow.

Martini capabilities used
  • API exposure
  • webhook consumption
  • data mapping
  • conditional routing
  • deduplication
  • monitoring

Pattern 4: Compare rates before freight tendering

When to use this pattern

Use this pattern when an order-management, procurement, or transportation workflow needs C.H. Robinson rate information before selecting a quote and booking freight.

Integration direction
Oracle Transportation Management
Martini
C.H. Robinson
Example Mapping
C.H. Robinson FieldCanonical FieldTarget Field
origin and destinationrateRequest.stopsRate request stops
weight, dimensions, and equipmentrateRequest.freightCharacteristicsRate criteria
quoted amount and currencyrateResult.amountAndCurrencyQuote value
rate identifier and expirationrateResult.externalReferenceSelected quote reference
Martini implementation pattern

Martini receives shipment characteristics, normalizes units and locations, requests rates, validates the response, and applies business rules for currency, expiration, carrier selection, or margin. It returns the selected result to the source system and retains the quote identifier for any subsequent booking operation.

Martini capabilities used
  • workflows
  • API consumption
  • mapping and transformation
  • business rules
  • validation
  • error handling

Applications commonly integrated with C.H. Robinson

C.H. Robinson transportation data can be coordinated with ERP, transportation-management, customer, visibility, and work-management applications. The following are practical enterprise integration targets; the exact direction and resource coverage depend on the Navisphere API product and the customer’s account configuration.

Application Scenario Direction Martini Pattern
SAP S/4HANA Exchange delivery-related transportation requests, freight costs, booking results, and shipment statuses with the ERP. SAP S/4HANA → Martini → C.H. Robinson Martini receives or retrieves delivery and shipment data from SAP, maps stops and freight attributes to Navisphere resources, submits rate or booking requests, and returns external identifiers and status updates with duplicate protection.
Oracle Transportation Management Coordinate shipments, rate requests, carrier selections, and transportation execution status between two logistics systems. Oracle Transportation Management → Martini → C.H. Robinson A Martini workflow orchestrates rate and booking calls, normalizes loads, shipments, stops, and carriers, and synchronizes status changes back to Oracle Transportation Management using a durable watermark and retry handling.
Salesforce Associate shipment bookings and delivery milestones with customer, order, and service records. Salesforce → Martini → C.H. Robinson Martini accepts booking requests from Salesforce or polls for relevant records, calls Navisphere REST endpoints, and routes tracking events or reconciled statuses back to Salesforce after applying field and lifecycle mappings.
ServiceNow Create or update operational work items when shipments are delayed, rejected, or require intervention. C.H. Robinson → Martini → ServiceNow Martini receives selected callbacks or performs scheduled status reconciliation, evaluates exception rules, and creates or updates ServiceNow work items while retaining the shipment, load, and event identifiers.
NetSuite Synchronize fulfillment-related transportation requests, freight charges, and delivery status with ERP transactions. NetSuite → Martini → C.H. Robinson Martini transforms NetSuite fulfillment data into shipment and stop requests, invokes Navisphere APIs, and writes booking and delivery outcomes back to the relevant NetSuite transactions with idempotent correlation keys.
project44 Combine C.H. Robinson transportation execution data with broader multimodal visibility and customer-facing tracking. C.H. Robinson → Martini → project44 Martini maps C.H. Robinson loads, shipments, stops, and tracking events into the visibility platform’s model, routes updates in the required direction, and reconciles missed events through scheduled retrieval.
FourKites Share shipment and carrier data with a visibility platform and receive normalized tracking milestones. C.H. Robinson → Martini → FourKites A Martini workflow consumes Navisphere data or selected callbacks, applies identifier and status transformations, sends the normalized payload to FourKites, and records delivery and retry outcomes.
Jira Create operational work items for shipment exceptions, integration failures, or carrier-management tasks. C.H. Robinson → Martini → Jira Martini evaluates non-success shipment or load states, enriches the exception with correlation data, and creates or updates Jira issues while routing transient failures through controlled retries.

How to build a C.H. Robinson integration in Martini

Objective

Establish secure access to the applicable Navisphere API product and keep environment-specific credentials outside workflow logic.

Instructions in Martini

  • Register the application with C.H. Robinson and confirm the required API permissions
  • Store OAuth client credentials and endpoint configuration in Martini secrets or environment configuration
  • Separate sandbox and production settings where both environments are available
  • Confirm token lifetime, scopes, rate limits, and supported resources

Objective

Select an event-driven, API-led, or scheduled entry point based on the required business process and callback coverage.

Instructions in Martini

  • Use an exposed Martini API for booking or rate requests from internal applications
  • Receive selected C.H. Robinson callbacks through a Martini API when enabled
  • Use a scheduler for incremental retrieval and reconciliation when callbacks are unavailable
  • Define the correlation and idempotency key before processing begins

Objective

Call the appropriate C.H. Robinson REST resource and handle pagination, filtering, and token reuse consistently.

Instructions in Martini

  • Acquire or reuse an OAuth 2.0 bearer token
  • Call the applicable rate, shipment, load, stop, carrier, or tracking resource
  • Apply supported modified-date, status, or event filters
  • Process continuation pages and distinguish empty results from incomplete retrievals

Objective

Coordinate the end-to-end Martini workflow from input validation through vendor calls, downstream writes, and state management.

Instructions in Martini

  • Validate required shipment, stop, rate, or event fields
  • Sequence dependent calls such as rate retrieval followed by booking
  • Persist external identifiers, event IDs, and synchronization watermarks
  • Route business exceptions separately from transient technical failures

Objective

Transform Navisphere payloads into canonical transportation models and target application structures without assuming identical lifecycles.

Instructions in Martini

  • Map loads, shipments, stops, quotes or rates, carriers, and tracking events explicitly
  • Normalize timestamps, currencies, units, locations, and status values
  • Preserve vendor identifiers and relevant unknown fields for audit or forward compatibility
  • Use mapping rules appropriate to each target application

Objective

Enforce business controls that prevent duplicate bookings, invalid requests, and incorrect status transitions.

Instructions in Martini

  • Check source-system idempotency keys before creating or booking shipments
  • Validate quote expiration, required stops, and supported status transitions
  • Use overlap windows for incremental synchronization
  • Deduplicate callback and tracking events when identifiers are supplied

Common C.H. Robinson data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
LoadsRepresent transportation movements managed through the C.H. Robinson network, including identifiers, status, locations, and carrier information.Oracle Transportation Management, SAP S/4HANA, NetSuite, project44Martini maps load identifiers and lifecycle values to canonical transportation models, persists correlation keys, and synchronizes changes through callbacks or incremental retrieval.
ShipmentsRepresent freight movements requiring booking, execution, delivery, and tracking.SAP S/4HANA, Salesforce, NetSuite, Oracle Transportation ManagementMartini validates shipment requests, maps stops and commercial attributes, invokes supported create or booking operations, and prevents duplicate submissions.
StopsIdentify pickup, delivery, and intermediate locations associated with a shipment or load.SAP S/4HANA, Oracle Transportation Management, FourKitesMartini normalizes location, sequence, appointment, and milestone fields while preserving vendor identifiers and handling optional stop structures.
Quotes or ratesRepresent transportation pricing and rate requests used before booking or tendering freight.SAP S/4HANA, NetSuite, Oracle Transportation ManagementMartini submits rate criteria, applies currency and unit transformations, preserves quote identifiers and expiration data, and routes selected results to the source system.
CarriersIdentify transportation providers associated with loads, tenders, or shipment execution.Oracle Transportation Management, project44, FourKitesMartini maps carrier identifiers and attributes where the API permits access and uses them in booking, visibility, and exception workflows.
Tracking eventsCapture shipment or load status, location, milestone, and delivery updates.Salesforce, ServiceNow, project44, FourKitesMartini deduplicates events, maps vendor statuses to an internal lifecycle, routes exceptions, and reconciles callback gaps through scheduled API queries.

Authentication and security considerations

OAuth 2.0 and application credentials

Navisphere uses application registration and OAuth 2.0 access tokens supplied as bearer tokens in the HTTP Authorization header. Required permissions, scopes, token lifetime, and grant details should be confirmed for the specific API product and account.

Credential protection

  • Store client credentials, tokens, and environment configuration in Martini secrets or secured environment configuration.
  • Keep sandbox and production credentials separate.
  • Do not place client secrets in payloads, mappings, logs, or source-controlled workflow definitions.
  • Sanitize shipment and authentication data in operational logs.

Operational considerations for C.H. Robinson integrations

Rate limits and pagination

Confirm limits for each Navisphere API and use bounded concurrency. Handle 429 responses and Retry-After values where supplied. Confirm whether each endpoint uses pages, offsets, cursors, or continuation links.

Synchronization and idempotency

Persist a last-successful watermark with an overlap window for late updates. Use stable source and vendor identifiers to prevent duplicate bookings, and deduplicate callback or tracking events when an event identifier is available.

Lifecycle and schema changes

Define explicit mappings for requested, quoted, booked, accepted, in-transit, delivered, cancelled, and exception states using the assigned API specification. Treat optional fields as nullable and avoid assuming that all shipment types have identical stops or carrier data.

Testing and observability

Test large result sets, timeout recovery, token renewal, rate limiting, duplicate requests, and callback gaps in a non-production environment. Capture sanitized correlation information, monitor workflow outcomes, and route non-retryable business errors to an exception process.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate more than individual API calls

Martini coordinates authentication, vendor API calls, validation, business rules, downstream writes, and synchronization state in maintainable workflows rather than scattering logic across scripts.

Support multiple integration modes

The same implementation can combine REST consumption, exposed APIs for internal callers or callbacks, scheduled reconciliation, and persistence of identifiers and watermarks. This is useful because C.H. Robinson callback coverage may be limited by API product and account configuration.

Improve reliability and reuse

  • Centralize mappings for loads, shipments, stops, rates, carriers, and tracking events.
  • Apply consistent idempotency, retry, pagination, and error-routing rules.
  • Keep credentials and environment settings separate from workflow definitions.
  • Reuse integration assets across ERP, TMS, visibility, customer, and operational applications.

Frequently asked questions

How can C.H. Robinson be integrated with enterprise systems?

C.H. Robinson’s Navisphere platform is primarily integrated through REST APIs for rates, shipment booking, loads, shipments, and tracking. Selected accounts or API products may also support callback or webhook-style notifications. OAuth 2.0 is the documented authentication model, and scheduled API retrieval can provide reconciliation when event coverage is incomplete.

Can Martini integrate with C.H. Robinson?

Yes. Martini can consume C.H. Robinson Navisphere REST APIs, authenticate with OAuth 2.0, expose an API for selected callbacks, orchestrate scheduled synchronization, and map transportation data into ERP, TMS, visibility, customer, or operational systems.

Do I need a connector to integrate C.H. Robinson with Martini?

No. A dedicated C.H. Robinson connector is not required. Martini can integrate using C.H. Robinson’s confirmed native REST APIs, OAuth 2.0 authentication, and selected webhook-style callbacks or other approved endpoints.

Is there any extra Lonti cost to integrate C.H. Robinson with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate C.H. Robinson. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from C.H. Robinson, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.

Which C.H. Robinson integration methods should be used?

Use the Navisphere REST APIs as the primary method for rates, shipments, loads, and tracking. Use webhook-style notifications when the relevant API product and account configuration support the required events, and use scheduled incremental REST retrieval for reconciliation. GraphQL and SOAP APIs are not confirmed, and direct database access is not supported.

Are C.H. Robinson webhooks available for every shipment event?

Not confirmed. C.H. Robinson event or callback capabilities may cover selected shipment or load events and depend on the API product and customer configuration. A resilient design combines callbacks, where available, with scheduled polling and reconciliation for events that are not delivered.

How does shipment synchronization work with C.H. Robinson?

A Martini workflow can retrieve recently changed loads or shipments using supported date, status, or last-modified filters, then map and upsert them into downstream systems. The workflow should persist a watermark, use an overlap window, process pagination, and periodically reconcile a wider time range.

How does Martini handle C.H. Robinson mapping, errors, and retries?

Martini maps vendor payloads into canonical shipment, load, stop, rate, carrier, and tracking models and applies target-specific transformations. Workflows can distinguish authentication, validation, rate-limit, transient, and business errors; retry safe transient failures, deduplicate events, and route non-retryable exceptions for operational review.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect C.H. Robinson with Martini

Use Martini to orchestrate C.H. Robinson Navisphere APIs, selected event callbacks, scheduled synchronization, and downstream transportation workflows with secure configuration and reusable integration logic.

EXPLORE MARTINI
BOOK A DEMO