Impala website screenshot

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 APIs on the APIs.io network: Bookings API, Hotels API, and Rate Calendar API. Tagged areas include Company, Hotels, Travel, Booking, and Hospitality.

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

1 APIs
CompanyHotelsTravelBookingHospitalityPaymentsDefunct

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 4

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

API Collection

OPEN COLLECTION

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

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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-09-03'
  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-07-19'
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:
  - 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: 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

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"

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.

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