Everything you need to ship faster

Introduction

Welcome to the MAPPIN API — the unified partner API gateway for global travel data. Aggregate countries, cities, and hotels from 6+ travel providers through one intelligent mapping layer. Built for speed, designed for scale.

Quickstart

Get up and running with MAPPIN in three quick steps.

1. Create an account

Head to the registration page and sign up as a partner. It takes under a minute — no credit card required.

2. Get your API key

After signing in, navigate to API Keys in your partner dashboard. Copy your key — you'll need it for every API request.

3. Make your first request

Try fetching the list of countries:

curl https://mappin.rpconnect.travel/api/countries/ \
  -H "X-API-Key: your_api_key_here"

You should get back a JSON response with all supported countries. That's it — you're integrated. 🎉

Authentication

All API requests must include your API key in the X-API-Key header. Requests without a valid key will be rejected with 401 Unauthorized.

GET /api/hotels/ HTTP/1.1
Host: mappin.rpconnect.travel
X-API-Key: your_api_key_here

cURL

curl https://mappin.rpconnect.travel/api/hotels/ \
  -H "X-API-Key: your_api_key_here"

Python

import requests

headers = {"X-API-Key": "your_api_key_here"}
response = requests.get(
    "https://mappin.rpconnect.travel/api/hotels/",
    headers=headers
)
print(response.json())

JavaScript

const response = await fetch(
  "https://mappin.rpconnect.travel/api/hotels/",
  { headers: { "X-API-Key": "your_api_key_here" } }
);
const data = await response.json();
console.log(data);

How It Works

MAPPIN sits between your application and multiple travel data providers (HotelBeds, Rezlive, and more). Instead of integrating each provider separately, you talk to one unified API and we handle:

• Provider aggregation — one request fetches from all your subscribed providers
• Data normalization — consistent JSON schema across every provider
• Master mapping — duplicate cities and hotels are automatically merged into a single canonical record
• Rate management — smart queuing so you never hit provider limits
• Real-time availability — always fresh, no stale caches

Rate Limits & Quotas

MAPPIN enforces three types of limits to keep the platform fast for everyone:

Error Handling

MAPPIN uses standard HTTP status codes. Errors always return a JSON body with an error field.

{
  "error": "Daily API quota exceeded"
}

Countries

Access the master list of countries supported by MAPPIN.

GET /api/countries/

Returns all countries in the master database.

curl https://mappin.rpconnect.travel/api/countries/ \
  -H "X-API-Key: your_api_key_here"

GET /api/countries/<country_code>/

Returns details for a specific country by ISO 2-letter code (e.g., GB, IN, US).

curl https://mappin.rpconnect.travel/api/countries/GB/ \
  -H "X-API-Key: your_api_key_here"

Cities

Search cities and fetch city details.

GET /api/cities/

Returns cities. Supports filtering:

• ?country=GB — filter by country code
• ?search=london — search by name

GET /api/cities/<city_id>/

Returns details for a specific city.

GET /api/city/?name=<name>

Legacy endpoint — search cities by name or fetch hotels by city_id.

Hotels

The core of MAPPIN — search hotels, get details, and access provider-normalized data.

GET /api/hotels/

List hotels. Supports filtering by city_id, country, and pagination.

curl "https://mappin.rpconnect.travel/api/hotels/?city_id=123" \
  -H "X-API-Key: your_api_key_here"

GET /api/hotels/<hotel_id>/

Returns full hotel details, including all provider mappings, rooms, images, and amenities.

Provider Mapping

GET /api/provider-map/

Look up how a specific hotel or city is mapped across different providers. Useful for debugging and reconciliation.

API Playground

Test any endpoint interactively without writing a single line of code. Log in to your dashboard and click API Playground in the sidebar.

Get Help

Stuck? We're here to help.

• 📧 Support: assist@rpconnect.travel