HeadOut

Headout is a global experiences marketplace that curates and sells tickets to tours, attractions, events, shows and activities across major cities worldwide. For developers, Headout operates a public Partner API (github.com/headout/api-docs) that lets affiliates and resellers browse the catalog (products, categories, collections and subcategories by city and language), pull live inventory and per-person/per-group pricing for a variant, and place bookings through a two-step create-then-capture flow. The API is versioned by URI path (v1 and v2 under /api/public/), authenticates with a Headout-Auth API key (pk_ production / tk_ sandbox), paginates with offset/limit, and returns a structured error envelope. A registrable seatmap iframe component is offered for seat selection. Headout is backed by 500 Global and Version One Ventures.

HeadOut publishes 6 API contracts indexed on the APIs.io network, including Booking API, Categories API, Collections API, and 3 more. Tagged areas include Travel, Tours and Activities, Experience, Attractions, and Ticketing.

HeadOut’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

33.8/100 thin ▬ flat Agent 26/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 published contract 2 Agent Skills

Travel Tours and Activities Experience Attractions Ticketing Booking Marketplace Partner API Affiliates Event

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 33.8/100 · thin

Contract Quality 2.9 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 5.8 / 17

Operational Transparency 1.5 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/headout/"><img src="https://apis.io/badge/headout/card.svg" alt="HeadOut on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 13.7 — up to +21.6 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Contract Governance scores 4.5 — up to +11.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/headout/apis.yml: open an issue on github.com/api-evangelist/headout to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
OCTO Tours, Activities & Attractions Connectivity (members, known implementations, self-certification)	standard	58.1	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

HeadOut Booking API

The Booking API from HeadOut — 2 operation(s) for booking.

HeadOut Categories API

The Categories API from HeadOut — 1 operation(s) for categories.

HeadOut Collections API

The Collections API from HeadOut — 1 operation(s) for collections.

HeadOut Inventory API

The Inventory API from HeadOut — 1 operation(s) for inventory.

HeadOut Products API

The Products API from HeadOut — 1 operation(s) for products.

HeadOut Subcategories API

The Subcategories API from HeadOut — 1 operation(s) for subcategories.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Headout Partner Booking API

OPEN COLLECTION

Headout Partner Booking Categories API

OPEN COLLECTION

Headout Partner Booking Collections API

OPEN COLLECTION

Headout Partner Booking Inventory API

OPEN COLLECTION

Headout Partner Booking Products API

OPEN COLLECTION

Headout Partner Booking Subcategories API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create and capture a booking

AGENT SKILL

Browse the catalog and price a variant

AGENT SKILL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Headout Partner Overlay

4 actions · update · headout-partner-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Headout Authentication

apiKey · 1 scheme

SECURITY

Headout Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Headout Agentic Access

9 operations · 2 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

DataModel

Components

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

Deprecation

Deprecation

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: headout
name: HeadOut
description: Headout is a global experiences marketplace that curates and sells tickets to tours, attractions, events, shows
  and activities across major cities worldwide. For developers, Headout operates a public Partner API (github.com/headout/api-docs)
  that lets affiliates and resellers browse the catalog (products, categories, collections and subcategories by city and language),
  pull live inventory and per-person/per-group pricing for a variant, and place bookings through a two-step create-then-capture
  flow. The API is versioned by URI path (v1 and v2 under /api/public/), authenticates with a Headout-Auth API key (pk_ production
  / tk_ sandbox), paginates with offset/limit, and returns a structured error envelope. A registrable seatmap iframe component
  is offered for seat selection. Headout is backed by 500 Global and Version One Ventures.
url: https://raw.githubusercontent.com/api-evangelist/headout/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
- version-one-ventures
x-tier: profiled
x-tier-reason: partner-api-enriched
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://cdn-imgix.headout.com/static-pages/logo.png
tags:
- Travel
- Tours and Activities
- Experience
- Attractions
- Ticketing
- Booking
- Marketplace
- Partner API
- Affiliates
- Event
tags_raw:
- Travel
- Tours and Activities
- Experiences
- Attractions
- Ticketing
- Bookings
- Marketplace
- Partner API
- Affiliate
- Events
apis:
- aid: headout:headout-booking-api
  name: HeadOut Booking API
  description: The Booking API from HeadOut — 2 operation(s) for booking.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Booking
  properties:
  - type: OpenAPI
    url: openapi/headout-booking-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
- aid: headout:headout-categories-api
  name: HeadOut Categories API
  description: The Categories API from HeadOut — 1 operation(s) for categories.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Categories
  properties:
  - type: OpenAPI
    url: openapi/headout-categories-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
- aid: headout:headout-collections-api
  name: HeadOut Collections API
  description: The Collections API from HeadOut — 1 operation(s) for collections.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Collection
  tags_raw:
  - Collections
  properties:
  - type: OpenAPI
    url: openapi/headout-collections-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
- aid: headout:headout-inventory-api
  name: HeadOut Inventory API
  description: The Inventory API from HeadOut — 1 operation(s) for inventory.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Inventory
  properties:
  - type: OpenAPI
    url: openapi/headout-inventory-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
- aid: headout:headout-products-api
  name: HeadOut Products API
  description: The Products API from HeadOut — 1 operation(s) for products.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Product
  tags_raw:
  - Products
  properties:
  - type: OpenAPI
    url: openapi/headout-products-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
- aid: headout:headout-subcategories-api
  name: HeadOut Subcategories API
  description: The Subcategories API from HeadOut — 1 operation(s) for subcategories.
  humanURL: https://github.com/headout/api-docs
  baseURL: https://www.headout.com/api/public/v2
  tags:
  - Subcategories
  properties:
  - type: OpenAPI
    url: openapi/headout-subcategories-api-openapi.yml
  - type: Documentation
    url: https://github.com/headout/api-docs
  - type: APIReference
    url: https://github.com/headout/api-docs/tree/master/apis
  - type: GettingStarted
    url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
  - type: Authentication
    url: authentication/headout-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://newsroom.headout.com/rss/
  type: BlogRSS
- type: AgenticAccess
  url: agentic-access/headout-agentic-access.yml
- type: DomainSecurity
  url: security/headout-domain-security.yml
- type: Website
  url: https://headout.com
- type: DeveloperPortal
  url: https://github.com/headout/api-docs
- type: Documentation
  url: https://github.com/headout/api-docs
- type: APIReference
  url: https://github.com/headout/api-docs/tree/master/apis
- type: GettingStarted
  url: https://github.com/headout/api-docs/wiki/Integration-flow-for-Partners
- type: GitHubOrganization
  url: https://github.com/headout
- type: Blog
  url: https://www.headout.com/blog/
- type: Support
  url: https://www.headout.com/help/
- type: SignUp
  url: https://partner.headout.com/affiliate/
- type: TermsOfService
  url: https://www.headout.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.headout.com/privacy-policy/
- type: Authentication
  url: authentication/headout-authentication.yml
- type: Conventions
  url: conventions/headout-conventions.yml
- type: Idempotency
  url: conventions/headout-conventions.yml
- type: ErrorCatalog
  url: errors/headout-error-codes.yml
- type: Lifecycle
  url: lifecycle/headout-lifecycle.yml
- type: Deprecation
  url: lifecycle/headout-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/headout-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/headout-llms.txt
- type: Overlay
  url: overlays/headout-partner-overlay.yaml
- type: Conformance
  url: conformance/headout-conformance.yml
- type: DataModel
  url: data-model/headout-data-model.yml
- type: Sandbox
  url: sandbox/headout-sandbox.yml
- type: Components
  url: components/headout-components.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

HeadOut API — frequently asked questions

Does HeadOut have an API?

Yes. APIs.io lists 6 APIs from HeadOut, including HeadOut Booking API, HeadOut Categories API and HeadOut Collections API, and 3 more.

Is there an OpenAPI specification for the HeadOut API?

Yes. APIs.io indexes 6 OpenAPI specifications for HeadOut, each linked for download from this page.

How do I authenticate with the HeadOut API?

HeadOut uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Headout Authentication.

Is the HeadOut API ready for AI agents?

HeadOut has a Kin Score of 33.8 out of 100 (thin) and an Agent Readiness score of 25.9 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/headout"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/headout/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/headout/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.