Orders endpoints in development
The Orders API endpoints are currently under active development. Request/response shapes may change.
Orders
Order history
Complete audit trail — every event in an order's lifecycle, timestamped and attributed.
GET
/v1/orders/{orderID}/historyRequires X-API-KeyReturns a chronological event log for any order — every action, timestamped and attributed.Event types include:
-
-
-
-
-
-
-
-
-
-
-
created — Order was created-
confirmed — Airline accepted the booking-
payment_submitted — Payment was processed-
ticketed — Tickets were issued-
cancelled — Order was cancelled-
modified — Changes were made (seats, ancillaries, dates)Actor attribution tells you who made each change:-
agency — Your integration-
airline — The carrier's system-
system — Norba's automated processes-
traveler — Self-service actionsThe history is immutable — events are appended, never modified. Use this for order tracking UIs, customer support debugging, reconciliation, and compliance audits.Request example
curl --request GET \
--url https://api.norba.io/v1/orders/{orderID}/history \
--header "X-API-Key: $NORBA_KEY"Response example
Response example
{
"events": [
{
"event_type": "created",
"occurred_at": "2026-06-20T14:30:00Z",
"actor": "agency"
},
{
"event_type": "ticketed",
"occurred_at": "2026-06-20T15:00:00Z",
"actor": "system"
}
]
}Authorization
X-API-KeystringRequiredOpaque API key issued from the Norba dashboard. Sent on every request as the
X-API-Key HTTP header. Missing or invalid keys are rejected with 401 Unauthorized.Path parameters
orderIDstringRequiredOrder ULID.
Example:
ord_01HVN9M5K...