About the Allbookers Connectivity APIs

The Allbookers Connectivity APIs enable approved channel managers and integration partners to exchange property-related data with the Allbookers platform. These APIs are intended for backend-to-backend communication and support operational workflows such as property connection, room and rate-plan mapping, inventory updates, pricing updates, stay restrictions, blackout controls, reservation retrieval, and selected messaging flows.

This documentation is intended for technical teams building and maintaining direct integrations with Allbookers. It explains how connected partners should structure requests, interpret responses, and work with the supported connectivity flows exposed by the platform.

Getting started

If you are integrating with Allbookers for the first time, start by reviewing the connection model, request format requirements, and the API groups relevant to your integration. Most partners will typically work with connection APIs, room and rate-plan mapping APIs, rates and availability updates, and reservation retrieval flows.

What we expect from connectivity partners

Connectivity partners are expected to maintain a reliable integration with Allbookers and to keep synchronized data accurate, timely, and operationally consistent. Integrations should be designed to support stable data exchange and to minimize mapping issues, failed synchronization, and duplicate or incomplete updates.

• Support the integration flows required for the connected properties.
• Keep room, rate-plan, availability, and reservation data synchronized.
• Use the documented request formats, headers, and payload structures.
• Handle validation failures, retries, and operational errors appropriately.
• Keep integrations aligned with the latest supported API behavior.

Access model

The Allbookers Connectivity APIs are intended for approved partner integrations and are not part of the public booking website or end-user account interface. In practice, these APIs are used as backend integration endpoints for trusted partner workflows such as the Bookersdesk connectivity flow.

Access may be enabled at the property integration level depending on the connection type and the supported capabilities for that partner. Depending on the integration setup, a partner may interact with one or more API groups such as connection management, room and rate mapping, rates and availability, reservations, and selected messaging or synchronization flows.

Base URL

All connectivity requests should be sent to the Allbookers API base URL. The specific endpoint path, request method, and payload structure are documented in the relevant API sections.

All production requests must use HTTPS.

Request and response formats

The currently documented Allbookers connectivity endpoints primarily use JSON request and response payloads for backend-to-backend communication. Partners should follow the documented format for each endpoint and ensure that request headers, payload structure, and character encoding are correct.

• JSON is used for the currently documented connectivity endpoints.
• All request bodies should use UTF-8 encoding.
• Clients should be tolerant of compatible response changes such as additional fields.

Some responses may return plain text or simple boolean values depending on the endpoint behavior, so each endpoint description should be followed closely.

Security

All connectivity traffic must be sent over HTTPS. The currently documented connectivity flows are intended for approved partner integrations and backend-to-backend communication, not for browser-based public website usage.

Partners should securely handle all integration-related identifiers, payloads, and operational data. Where infrastructure-level restrictions are used, only trusted systems should be allowed to interact with the documented endpoints.

Rate limiting

To help protect platform stability and ensure fair usage, Allbookers may apply operational request limits to connectivity traffic. Integrations should avoid unnecessary polling, duplicate submissions, and burst traffic against the same resources.

When possible, partners should design retry behavior carefully and avoid repeated requests that can cause unnecessary load or conflicting updates.

Common request issues

The most common integration issues are typically caused by invalid identifiers, incorrect payload structure, missing required fields, mismatched room or rate-plan mappings, or unsupported date ranges.

• Missing or invalid propertyId
• Missing or invalid roomId
• Missing or invalid ratePlanId
• Empty request payloads for inventory or restriction updates
• Incorrect Content-Type header
• Invalid date format or unsupported date range

Partners should validate requests before sending them and confirm that the endpoint-specific format matches the documented contract.

Going live

Before going live, partners should verify that the required connectivity flows are working correctly for the connected properties. At minimum, this usually includes property connection, room and rate-plan mapping, inventory updates, pricing updates, stay restrictions, blackout handling, and reservation retrieval.

• Confirm that property and room mappings are correct.
• Verify that price and availability updates are applied as expected.
• Test stay restrictions and blackout updates.
• Validate reservation retrieval and downstream handling.
• Review retry behavior and failure handling before production use.

Disclaimer

This documentation describes the currently supported Allbookers connectivity flows for approved integration partners. Endpoint behavior, payload structure, and operational requirements may evolve as the platform and partner integrations continue to develop.