# About the API

## What is the Distribution API?

The Distribution API is MeetingPackage’s public demand-side API. It exposes venue content and provides two complementary booking capabilities:

* **RFP integration** – Submit structured Requests for Proposal (RFPs) that create group requests and tentative bookings, which venues then manage based on real availability.
* **Direct bookings** – Perform real-time availability searches and create or manage single-day meeting room bookings.


These represent two booking modes supported through the same API:

* **RFP (lead-driven)** – No API-level availability check; venues confirm or decline based on real inventory.
* **Direct bookings (availability-driven)** – Real-time availability and pricing, with instant confirmation where supported.


Partners authenticate using API keys and can access only the venues made visible to them through configuration.


```mermaid
sequenceDiagram
    participant Partner as Partner system
    participant MP as MeetingPackage

    Note over Partner: Choose an integration path

    Partner->>MP: Option 1: RFP flow (lead-driven)
    Note right of MP: Submit RFPs, retrieve <br>proposals via booking <br>operations

    Partner->>MP: Option 2: Direct bookings (availability-driven)
    Note right of MP: Check availability, create <br>orders, receive updates
```

#### Content distribution

Before performing either booking flow, partners use the API to retrieve venue content — such as venues, meeting spaces, floorplans, items and packages — scoped to the venues they are permitted to access.
This content forms the basis for search, availability, pricing and quoting across both the RFP and Direct Booking workflows.

## Who is this for?

* Distribution partners and enterprise clients integrating with MeetingPackage
* Developers, solution architects and product managers


## Value proposition

#### For partners

(Travel Management Companies, Meetings & Events platforms, Online Travel Agencies, Marketplaces)

* **Faster time to market** – MP-built RFP mappers reduce engineering effort.
* **One API, two booking modes** – Support instant booking and RFP within a single integration.
* **Improved conversion and response times** – Real-time availability and webhooks accelerate booking flows.
* **Operational efficiency** – Webhooks reduce polling; unified endpoints simplify maintenance.
* **Flexible distribution control** – Venue-visibility scoping and source-based isolation maintain channel boundaries.
* **Future-proofing** – Versioned endpoints and a published specification reduce upgrade risk.


#### For venues

* **Incremental demand** – Access to partner channels without bespoke integrations.
* **Centralized configuration** – Control booking mode, business hours, pricing and availability in one place.
* **Data consistency** – A single system of record for content, inventory and booking states.


#### For end customers

* Faster confirmations when instant booking is available.
* Clear workflows when an RFP is required.
* Accurate inventory and pricing with time-window specificity.
* A consistent experience across channels.