Discover/Chrobinson API
live

Chrobinson APIchrobinson.com

Search available freight loads, get real-time load board stats, and retrieve carrier services from C.H. Robinson via a single REST API.

Endpoint health
verified 15h ago
get_carrier_services
get_industries
get_location_autocomplete
get_load_board_stats
get_freight_services
6/6 passing latest checkself-healing
Endpoints
6
Updated
22d ago

What is the Chrobinson API?

This API exposes 6 endpoints covering C.H. Robinson's public load board, returning shipment details across origin, destination, equipment type, weight, and distance. The search_loads endpoint accepts origin city/state, pickup date range, and equipment type to return matching shipments and a total count, while get_load_board_stats surfaces live aggregate counts for dry van, reefer, and flatbed loads without any query parameters.

Try it
Shipping mode. A for All.
Number of results per page
Pickup date range end in YYYY-MM-DD format. Defaults to tomorrow (UTC).
Origin city name
Origin US state code (two-letter, e.g. IL)
Pickup date range start in YYYY-MM-DD format. Defaults to today (UTC).
Origin search radius in miles
Trailer equipment type filter: Van, Flatbed, or Reefer
Origin latitude
Destination city name
Origin longitude
Destination US state code (two-letter, e.g. TX)
Destination search radius in miles
Destination latitude
Destination longitude
api.parse.bot/scraper/51f78174-cf11-4299-ae0c-0c59fd644885/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X POST 'https://api.parse.bot/scraper/51f78174-cf11-4299-ae0c-0c59fd644885/search_loads' \
  -H 'X-API-Key: $PARSE_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "mode": "A",
  "page_size": "20",
  "origin_city": "Chicago",
  "origin_state": "IL",
  "origin_latitude": "41.8781",
  "origin_longitude": "-87.6298"
}'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace chrobinson-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: C.H. Robinson load board — search loads, autocomplete, stats, catalog."""
from parse_apis.c.h._robinson_logistics_api import CHRobinson, EquipmentType, LocationNotFound

client = CHRobinson()

# Get current load board statistics (total loads, by equipment type).
stats = client.loadboards.stats()
print(f"Total loads: {stats.total_available_loads}, Dry Van: {stats.dry_van_loads}")

# Autocomplete a city to get coordinates for searching loads.
location = client.loadboards.autocomplete(query="Dallas", limit=3).first()
if location:
    print(f"Found: {location.display_name} ({location.latitude}, {location.longitude})")

    # Search Van loads originating near the resolved location.
    for shipment in client.loadboards.search(
        origin_city=location.city_name,
        origin_state=location.state_province_code,
        origin_latitude=location.latitude,
        origin_longitude=location.longitude,
        equipment_type=EquipmentType.VAN,
        limit=3,
    ):
        print(f"Load {shipment.external_shipment_id}: {shipment.origin.city}, {shipment.origin.state_code} → "
              f"{shipment.destination.city}, {shipment.destination.state_code} | "
              f"{shipment.distance_miles} mi, {shipment.weight_pounds} lbs")

# Browse the freight services catalog.
for svc in client.catalogs.freight_services(limit=5):
    print(f"Service: {svc.name}")

# Retrieve carrier programs and technology info.
try:
    carrier = client.catalogs.carrier_services()
    print(f"Carrier tech: {carrier.technology}, Programs: {carrier.programs}")
except LocationNotFound as exc:
    print(f"Not found: {exc}")

# List industry verticals served.
for ind in client.catalogs.industries(limit=3):
    print(f"Industry: {ind.name} ({ind.url})")

print("Exercised: loadboards.stats / autocomplete / search, catalogs.freight_services / carrier_services / industries")
All endpoints · 6 totalmissing one? ·

Search for available freight loads on the public load board. Returns a list of shipments with origin, destination, distance, weight, and equipment details. Requires origin coordinates and city/state. Optionally filter by destination, equipment type, and pickup dates. Destination coordinates must be provided in the request body only (not query params) to avoid upstream 500 errors.

Input
ParamTypeDescription
modestringShipping mode. A for All.
page_sizeintegerNumber of results per page
pickup_endstringPickup date range end in YYYY-MM-DD format. Defaults to tomorrow (UTC).
origin_cityrequiredstringOrigin city name
origin_staterequiredstringOrigin US state code (two-letter, e.g. IL)
pickup_startstringPickup date range start in YYYY-MM-DD format. Defaults to today (UTC).
origin_radiusintegerOrigin search radius in miles
equipment_typestringTrailer equipment type filter: Van, Flatbed, or Reefer
origin_latituderequirednumberOrigin latitude
destination_citystringDestination city name
origin_longituderequirednumberOrigin longitude
destination_statestringDestination US state code (two-letter, e.g. TX)
destination_radiusintegerDestination search radius in miles
destination_latitudenumberDestination latitude
destination_longitudenumberDestination longitude
Response
{
  "type": "object",
  "fields": {
    "shipments": "array of shipment objects with origin, destination, distance, weight, equipment, modes, stops, and activityDate",
    "totalShipmentCount": "integer total number of matching shipments"
  },
  "sample": {
    "data": {
      "shipments": [
        {
          "modes": [
            "V"
          ],
          "stops": [
            {
              "stopType": "1",
              "warehouseInformation": {
                "city": "Salt Lake City",
                "openTime": "06:00:00",
                "closeTime": "15:00:00",
                "stateCode": "UT",
                "countryCode": "US"
              },
              "isScheduledOpenTimeSpecified": true,
              "calculatedArriveByEndDateTime": "2026-06-15T15:00:00",
              "isScheduledCloseTimeSpecified": true,
              "calculatedArriveByStartDateTime": "2026-06-15T06:00:00"
            }
          ],
          "origin": {
            "city": "Carol Stream",
            "stateCode": "IL",
            "coordinate": {
              "sOriginDeadHead": ""
            },
            "countryCode": "US"
          },
          "weight": {
            "pounds": 44000
          },
          "distance": {
            "miles": 1370
          },
          "equipment": {
            "width": {
              "standard": 0
            },
            "height": {
              "standard": 0
            },
            "length": {
              "standard": 53
            }
          },
          "destination": {
            "city": "Salt Lake City",
            "stateCode": "UT",
            "countryCode": "US"
          },
          "activityDate": "2026-06-12T00:00:00",
          "externalShipmentId": "dbe0081d-fca2-3d6d-2071-6ea5551c820d"
        }
      ],
      "totalShipmentCount": 556
    },
    "status": "success"
  }
}

About the Chrobinson API

Load Search and Board Statistics

The search_loads endpoint accepts origin_city, origin_state, and optional parameters including equipment_type (Van, Flatbed, Reefer), origin_radius, pickup_start/pickup_end in YYYY-MM-DD format, and a page_size for pagination. It returns an array of shipment objects — each carrying origin, destination, distance, weight, equipment details, modes, stop count, and activityDate — alongside a totalShipmentCount integer for the full result set. Note that destination coordinates must be passed in the request body, not as query parameters, to avoid server errors.

get_load_board_stats requires no inputs and returns four comma-formatted string fields: total_available_loads, dry_van_loads, reefer_loads, and flatbed_loads. These reflect current aggregate counts from the public load board.

Location Autocomplete

The get_location_autocomplete endpoint accepts a query string (city name or postal code) and returns an array of location objects. Each object includes displayName, coordinate (latitude and longitude), cityName, stateProvinceCode, countryCode, and country. This is useful for building origin/destination inputs before calling search_loads.

Services and Industry Catalog

Three catalog endpoints return static data about C.H. Robinson's offerings. get_freight_services returns a services array with each service's name and URL path. get_carrier_services returns a structured carrier_services object segmented into financial_services, programs, technology, and onboarding arrays. get_industries returns an industries array listing the vertical markets C.H. Robinson serves, each with a name and URL path.

Reliability & maintenanceVerified

The Chrobinson API is a managed, monitored endpoint for chrobinson.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when chrobinson.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official chrobinson.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
15h ago
Latest check
6/6 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor available flatbed load counts in real time using get_load_board_stats for carrier dispatch dashboards.
  • Filter freight shipments by equipment type and pickup date range using search_loads for load matching tools.
  • Build origin/destination autocomplete inputs using get_location_autocomplete with city or ZIP query strings.
  • Map load density by origin state and equipment type by paginating through search_loads results.
  • Aggregate carrier financial programs and technology offerings from get_carrier_services for competitive research.
  • Enumerate industry verticals served by a major 3PL using get_industries for market segmentation analysis.
  • Track changes in total available loads over time by polling get_load_board_stats on a schedule.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does C.H. Robinson have an official developer API?+
C.H. Robinson offers a developer portal at developer.chrobinson.com with APIs for carriers and shippers, but those require a business account and formal onboarding. This Parse API provides access to publicly available load board and service data without that requirement.
What does the `search_loads` endpoint return for each shipment?+
Each shipment object in the shipments array includes origin and destination details, distance, weight, equipment type, available shipping modes, stop information, and an activityDate. The totalShipmentCount field gives the full count of matching loads regardless of page_size.
Does the API return individual load pricing or rate quotes?+
Not currently. The search_loads endpoint returns shipment metadata including weight, equipment, and routing — but no rate or price fields are included in the response. You can fork this API on Parse and revise it to add a rate-retrieval endpoint if that data becomes accessible.
Can I search loads by destination city rather than just origin?+
The search_loads endpoint is structured around origin parameters (origin_city, origin_state, origin_radius). Destination filtering isn't exposed as a named input parameter. You can fork the API on Parse and revise it to add destination-based filtering if that capability is needed.
How should I handle the coordinate requirement for destination in `search_loads`?+
Destination coordinates must be included in the POST request body. Passing them as query parameters causes upstream server errors. Use get_location_autocomplete first to resolve a destination city to its latitude/longitude, then include those coordinates in the body of your search_loads request.
Page content last updated . Spec covers 6 endpoints from chrobinson.com.
Related APIs in MarketplaceSee all →
jbhunt.com API
Track your J.B. Hunt shipments in real-time for both business and home deliveries, search for service information across their site, and access freight class and location data for LTL quoting. Get company information and reference data to support your logistics and shipping needs.
dat.com API
Track real-time market conditions, fuel prices, and freight rate trends to make data-driven logistics decisions. Access industry insights through blog posts and resource materials to stay informed on transportation market dynamics.
flexport.com API
Get real-time air and ocean freight rates, search shipping routes, and access logistics service information to compare pricing and plan international shipments. Discover popular routes and retrieve freight rate quotes for any origin-destination pair.
chirojobs.com API
Search and browse chiropractic job listings with detailed information, explore job categories, and access ChiroJobs blog content and pricing—all in one place. Find related positions, compare opportunities, and stay informed with the latest industry insights.
royalcaribbean.com API
Search and compare Royal Caribbean cruises by destination, ship, itinerary, and price. Access detailed sailing information including port schedules, voyage durations, and fares across all global routes and departure dates.
chownow.com API
Search for nearby restaurants, view their operating hours and delivery zones, and browse complete menus with all items, modifiers, and prices. Access detailed restaurant information and locations to find exactly what you're looking for on the ChowNow marketplace.
cma-cgm.com API
Track shipping routes and vessel schedules across CMA CGM's 280+ shipping lines, including detailed port-to-port rotations, fleet information, and service specifics. Search for specific routes or browse complete shipping schedules to plan logistics and monitor maritime transportation options.
maersk.com API
Track your Maersk shipping containers in real-time, monitor vessel schedules and locations, and discover available routes between ports and countries. Access comprehensive port data, search for specific locations, and view detailed shipping route information to plan your logistics more effectively.