Search flights across selected providers
Feature-gated system-managed capability router. Locus plans eligible providers, executes them concurrently, normalizes and deduplicates itineraries, ranks offers, and returns aggregate billing. Use the preview route first when you need an estimate. A narrower request maxCredits or credential-level ceiling prevents dispatch when the aggregate estimate is too high. Retries must reuse the same Idempotency-Key and identical logical request; a 202 response means one or more child providers are still processing, so retry with the same key.
Request
- Base URLhttps://api.paywithlocus.com/api
- URLhttps://api.paywithlocus.com/api/wrapped/credits/locus-travel/flight-search
- Auth
- HTTP bearer
- or HTTP bearer
- or HTTP bearer
- or HTTP bearer
Headers
Required only when the end-user JWT carries sid. Send the original high-entropy session value; sid is its SHA-256 fingerprint. Ignored for secret-key authentication.
One key per logical travel search. Reuse it with an identical request to replay or finish the run.
Case-sensitive immutable ID in the tenant namespace. Prefer an identity-provider subject, not an email address.
Optional end-user identity for a tenant secret or sandbox key. It must agree with body externalUserId when both are present.
Request body
Response
Normalized, ranked flight search with provider outcomes and aggregate billing
Changes
No recorded changes to this operation across all 1 revision of this API.