Orders endpoints in development
The Orders API endpoints are currently under active development. Request/response shapes may change.
Orders
Reshop order
Find alternatives for an existing booking — new dates, different routing.
POST
/v1/orders/{orderID}/reshopRequires X-API-KeyPlans change. When a traveler needs to modify their itinerary, use Reshop to search for alternative flights against an existing order.What you can change:
- New departure date
- New return date
- Different origin airport
- Different destination airportThe response returns offers in the same shape as the main shopping endpoint, making it easy to show side-by-side comparisons in your UI.Combine with
- New departure date
- New return date
- Different origin airport
- Different destination airportThe response returns offers in the same shape as the main shopping endpoint, making it easy to show side-by-side comparisons in your UI.Combine with
POST /v1/orders/{orderID}/change (action reissue) to apply the selected alternative. Reshop does not modify the original order — it only searches for options.Request example
curl --request POST \
--url https://api.norba.io/v1/orders/{orderID}/reshop \
--header "X-API-Key: $NORBA_KEY" \
--header "Content-Type: application/json" \
--data '{ "new_departure_date": "2026-07-16" }'Response example
Response example
{ "offers": [ /* ... */ ] }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...Request body
new_departure_datestringNew departure date (YYYY-MM-DD).
new_return_datestringNew return date.
new_originstringNew origin airport.
new_destinationstringNew destination airport.