Skip to main content
An order transaction groups the orders that belong to one patient testing journey. Every newly created initial order starts an order transaction, and related orders—such as supported redraws—join that transaction. For the complete integration sequence from order creation through result retrieval, see Orders and Results.

​
Relationship to orders

  • An initial order has origin: initial and is not derived from another order.
  • Every order belongs to exactly one order transaction.
  • One order transaction contains at least its initial order and can contain related orders.
  • Each order retains its own lifecycle, events, and results.
  • Transaction result endpoints combine results across the related orders.
Store both order.id and order_transaction.id from the Create Order response. Use the transaction ID as the stable grouping key for the full testing journey and the order ID for operations on an individual order. Related orders, including supported redraws, retain separate order IDs and join the same transaction.

​
Transaction statuses

The transaction status summarizes the group. Continue to use each order’s status and events when your workflow depends on the progress of an individual order.

​
API endpoints

The following endpoints are available to retrieve order transaction information and combined results for all orders within a transaction: Responses for the following endpoints also include order transaction details:
  • Get Orders — List and filter orders, including by order transaction ID.
  • Get Order — Retrieve an individual order.
  • Get Order Results — Retrieve an individual order’s results.