HeadOut · Authentication Profile

Headout Authentication

Authentication

HeadOut secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

TravelTours and ActivitiesExperiencesAttractionsTicketingBookingsMarketplacePartner APIAffiliateEvents
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

HeadoutAuth apiKey
· in: header (Headout-Auth)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: openapi/headout-partner-openapi.yml
docs: https://github.com/headout/api-docs/blob/master/conventions/basics.md
notes: >-
  All Partner APIs authenticate with the Headout-Auth request header carrying an
  API token. Production tokens are prefixed pk_ (live bookings), testing tokens
  tk_ (sandbox). V2 requires auth on every call; some V1 read endpoints (e.g.
  inventory) are optional but auth is recommended. Keys are issued by email via
  partnerships@headout.com / apikey@headout.com. No OAuth surface.
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: HeadoutAuth
  type: apiKey
  in: header
  parameter: Headout-Auth
  description: API token. Production keys are prefixed pk_, testing keys tk_.
  sources:
  - openapi/headout-partner-openapi.yml