Order exports

Use GET /v2/reports/orders for bulk exports, finance workflows, and reporting. It is not the best resource for a live order view. The endpoint requires the reports:read scope and returns one report row for each order. Read the order resource when you need the complete current state of one order.

Select report rows

Use created_from and created_to to select a creation-time range. Send RFC 3339 timestamps with an offset. Use page_size to select a page size. The allowed range is 1 to 100.

Read every page

Process data, then read has_more. When has_more is true, send the returned next_cursor in the next request. Use the cursor without modification. Stop when has_more is false. Do not set an arbitrary client-side page limit for a complete export. This Node.js example writes one JSON row per line. Set BAHN_ACCESS_TOKEN to a token with reports:read and redirect standard output to a file when needed.

const url = new URL("https://sandbox.api.bahnexpress.fi/v2/reports/orders")
url.searchParams.set("page_size", "100")
url.searchParams.set("created_from", "2026-08-01T00:00:00+03:00")
url.searchParams.set("created_to", "2026-08-31T23:59:59.999+03:00")

while (true) {
  const response = await fetch(url, {
    headers: { Authorization: `Bearer ${process.env.BAHN_ACCESS_TOKEN}` },
  })
  if (!response.ok) throw new Error(await response.text())
  const page = await response.json()
  for (const row of page.data) console.log(JSON.stringify(row))
  if (!page.has_more) break
  if (!page.next_cursor) throw new Error("The next page cursor is missing.")
  url.searchParams.set("cursor", page.next_cursor)
}

Both date bounds are inclusive. The example preserves its date filters on every page. For a long export, use the token cache and renewal flow and the retry rules. The same pagination loop works for /v2/orders, using that endpoint’s filters and the orders:read scope. Order summaries and report rows have different fields.

Use report fields

Each row groups these fields:

Group	Examples
Identity	Bahn order ID, customer reference, `ordered_for`, and order actor
Vehicle	VIN and registration number
Route	Countries and formatted addresses
Time	Created, available, pickup, and delivery times
Transport	Distance and duration values
Cost	Currency and total cents
Refuel	Refuel occurrence and cost

The ordered_for value identifies the business an ordering channel ordered for. It is null when the order belongs to the credential’s own account. The ordered_by value identifies the API credential for a Customer API order. Treat a missing optional value as unavailable.

Get started

Create and manage orders

Follow the transport

Reliability and production

Platform ordering

Automation

Select report rows

Read every page

Use report fields

​Select report rows

​Read every page

​Use report fields

Select report rows

Read every page

Use report fields