Corridors

GET /corridors lists every known directed corridor. It is a bulk, unpaginated export of the full inventory — treat it as a download and cache it, not a browsing API.

GET /api/v1/corridors lists every known corridor — a directed origin→destination lane (see How APEX works). The reverse direction is a separate corridor.

This endpoint is unpaginated — it returns the entire corridor inventory (hundreds of thousands of rows, tens of megabytes of JSON). Treat it as a bulk export, not a browsing API: fetch it occasionally and cache the result. Pagination is a known gap.

{
  "corridors": [
    {
      "id": "da0d787c-2a81-4d4b-8c88-330c765dc42e",
      "name": "'S Gravenwezel, BE → Bartholomä, DE",
      "loading_country": "BE",
      "unloading_country": "DE",
      "loading_location_id": "ee93f39a-d11a-44a2-9cf6-6b3d2b346452",
      "unloading_location_id": "d5edbfc0-60ed-4072-9469-772ccb1a732f",
      "is_active": true,
      "created_at": "2026-05-27T19:07:08.924422Z"
    }
  ],
  "total": 305758
}

To query prices for a specific corridor over time, use the corridor analytics endpoints — trends and statistics — rather than scanning this inventory.