> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bahnexpress.fi/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For Bahn Customer API V2 integration work, start with /skill.md and /guides/agent-integration.md on this documentation site. Use /llms.txt to find the guides for the requested workflow.
> The main integration orders your company's transports from existing software. Follow the requested screen, service, or job. Omit ordered_for for own-account orders. Use the platform-ordering guide to choose order ownership and billing for businesses using a platform. Add a customer-facing interface only when requested.
> Use /openapi.yaml for paths, schemas, scopes, and operation preconditions. Use the guides for transport rules and recovery behavior. Load only the relevant pages.
> Use the sandbox for development and tests. Keep credentials on the server. Production orders start real transport work; follow the customer's authorized workflow and account context.
> For required writes, preserve write keys and request data across retries, and use current actions and quoted revisions for order changes. When consuming webhooks, verify and durably store them before acknowledgement.
> Deliver the implemented workflow with test evidence, setup steps, and remaining gaps. Distinguish simulated checks from requests actually verified against Bahn.

# Changelog

> Changes to the Bahn Customer API and its documentation.

<Update label="5 October 2026" description="API V2">
  ## Driver assignment

  * A new order status, `driver_assigned`, shows that at least one driver booked part of the order before pickup.
  * A new order field, `driver_assignments`, lists each booked driver's name and the vehicle and part of the route that the driver covers.
  * Changes and self-service cancellation now close permanently at the first driver booking. If the driver unbooks, they stay closed.
  * A new order field, `cancellation_unavailable_reason`, explains why changes and cancellation are closed.
  * The first driver booking, and the last unbooking before pickup, send `com.bahn.order.status.changed.v1`. Other changes to the drivers send `com.bahn.order.updated.v1`. There is no new event type.

  API V1 order status values did not change. V1 cancellation follows the same rule and closes at the first driver booking.

  Read [Order status and driver assignment](/guides/order-status) and [Change or cancel an order](/guides/manage-orders).

  ## Documentation

  * The API reference uses Mintlify's standard reference layout.
  * New guides explain [order status](/guides/order-status), [changes and cancellation](/guides/manage-orders), and [pickup and delivery times](/guides/timing).
</Update>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.