Impala

Impala built a single, standardized REST API for the hotel industry — one integration to search availability, read rate plans, and create, amend, and cancel bookings across many property management systems (PMS), so any app could sell hotel rooms and earn commission per booking. Founded in London in 2016 and backed by Speedinvest, Lakestar, and Kima Ventures, Impala shipped a sandbox (with a demo hotel, "The Charleston"), a Postman collection, and PHP/JavaScript wrappers. The company is now defunct: getimpala.com / impala.travel and the API and docs hosts no longer resolve, and the primary domain is held by an unrelated party. This profile preserves the historical OpenAPI (apis.guru impala.travel:hotels 1.003) and pipeline-derived artifacts for the record.

Impala publishes 3 API contracts indexed on the APIs.io network: Bookings API, Hotels API, and Rate Calendar API. Tagged areas include Company, Hotels, Travel, Booking, and Hospitality.

The Impala catalog on APIs.io includes 1 Spectral governance ruleset.

Impala’s developer surface includes authentication, sandbox, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

0.0/100 minimal ▬ flat Agent 0/100 human only Front door AI 1/6 silent Heartbeat 0/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Hotels Travel Booking Hospitality Payments Defunct

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Reservation & Booking Management

BC-4020

Bookings

POST /bookings DELETE /bookings/{bookingId} PUT /bookings/{bookingId}

Travel Product & Inventory Management

BC-4000

Hotels

GET /hotels

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 0.0/100 · minimal

Contract Quality 0.0 / 19

Developer Ergonomics 0.0 / 15

Access Clarity 0.0 / 15

Operational Transparency 0.0 / 10

Contract Governance 0.0 / 9

Discoverability 0.0 / 8

Regulatory Posture 1.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 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

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/impala/"><img src="https://apis.io/badge/impala/card.svg" alt="Impala 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
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)
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 0.0 — up to +25.0 composite points
Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 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/impala/apis.yml: open an issue on github.com/api-evangelist/impala 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
APIs.guru OpenAPI Directory (API definition directory)	standard	26.8 (thin)	-	-

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.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

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

Impala Bookings API

Making and managing bookings.

Impala Hotels API

Accessing hotel content, available rooms and rates.

Impala Rate Calendar API

Getting rates for future dates.

Open Collections 3

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

Impala Hotel Booking Bookings API

OPEN COLLECTION

Impala Hotel Booking Bookings Hotels API

OPEN COLLECTION

Impala Hotel Booking Bookings Rate Calendar API

OPEN COLLECTION

Agent Skills 2

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

Retrieve, amend, or cancel a booking

AGENT SKILL

Search hotels and create a booking

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Impala API Rules

70 rules · 60 errors 8 warnings 2 info

SPECTRAL

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.

Impala Hotels Overlay

2 actions · update · impala-hotels-openapi-original.json

DERIVED

Security Posture 1

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

Impala Authentication

apiKey/http · 2 schemes

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Sandbox

Sandbox

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

GitHubOrganization

GitHubOrganization

Postman

Postman

Access & Security 1

Authentication, authorization, and security posture

Authentication

Authentication

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: impala
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/impala.png
name: Impala
description: 'Impala built a single, standardized REST API for the hotel industry — one integration to search availability,
  read rate plans, and create, amend, and cancel bookings across many property management systems (PMS), so any app could
  sell hotel rooms and earn commission per booking. Founded in London in 2016 and backed by Speedinvest, Lakestar, and Kima
  Ventures, Impala shipped a sandbox (with a demo hotel, "The Charleston"), a Postman collection, and PHP/JavaScript wrappers.
  The company is now defunct: getimpala.com / impala.travel and the API and docs hosts no longer resolve, and the primary
  domain is held by an unrelated party. This profile preserves the historical OpenAPI (apis.guru impala.travel:hotels 1.003)
  and pipeline-derived artifacts for the record.'
url: https://raw.githubusercontent.com/api-evangelist/impala/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- speedinvest
x-tier: stub
x-tier-reason: portfolio-lead
x-status: defunct
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
tags:
- Company
- Hotels
- Travel
- Booking
- Hospitality
- Payments
- Defunct
apis:
- aid: impala:impala-bookings-api
  name: Impala Bookings API
  description: Making and managing bookings.
  humanURL: https://www.postman.com/getimpala/impala-hotel-booking-api/documentation/fdkbiih/impala-hotel-booking-api
  baseURL: https://api.impala.travel/v1
  tags:
  - Booking
  tags_raw:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/impala-bookings-api-openapi.yml
- aid: impala:impala-hotels-api
  name: Impala Hotels API
  description: Accessing hotel content, available rooms and rates.
  humanURL: https://www.postman.com/getimpala/impala-hotel-booking-api/documentation/fdkbiih/impala-hotel-booking-api
  baseURL: https://api.impala.travel/v1
  tags:
  - Hotels
  properties:
  - type: OpenAPI
    url: openapi/impala-hotels-api-openapi.yml
- aid: impala:impala-rate-calendar-api
  name: Impala Rate Calendar API
  description: Getting rates for future dates.
  humanURL: https://www.postman.com/getimpala/impala-hotel-booking-api/documentation/fdkbiih/impala-hotel-booking-api
  baseURL: https://api.impala.travel/v1
  tags:
  - Rate Calendar
  properties:
  - type: OpenAPI
    url: openapi/impala-rate-calendar-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://impala.travel
- type: CapabilityMap
  url: capabilities/impala-capability-edges.yml
  name: Impala Business Capability Map
- type: Overlay
  url: overlays/impala-hotels-overlay.yaml
- type: Authentication
  url: authentication/impala-authentication.yml
- type: Packages
  url: packages/impala-packages.yml
- type: SDKs
  url: packages/impala-packages.yml
- type: X-MCPServerCandidate
  url: mcp/impala-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/impala-llms.txt
- type: Conventions
  url: conventions/impala-conventions.yml
- type: ErrorCatalog
  url: errors/impala-problem-types.yml
- type: Lifecycle
  url: lifecycle/impala-lifecycle.yml
- type: Conformance
  url: conformance/impala-conformance.yml
- type: DataModel
  url: data-model/impala-data-model.yml
- type: Sandbox
  url: sandbox/impala-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: GitHubOrganization
  url: https://github.com/GetImpala
- type: Postman
  url: https://www.postman.com/getimpala/impala-hotel-booking-api/documentation/fdkbiih/impala-hotel-booking-api
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Impala API — frequently asked questions

Does Impala have an API?

Yes. APIs.io lists 3 APIs from Impala, including Impala Bookings API, Impala Hotels API and Impala Rate Calendar API.

Is there an OpenAPI specification for the Impala API?

Yes. APIs.io indexes 3 OpenAPI specifications for Impala, each linked for download from this page.

How do I authenticate with the Impala API?

Impala uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Impala Authentication.

Is the Impala API ready for AI agents?

Impala has a Kin Score of 0.0 out of 100 (minimal) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.

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/impala"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.