API & Developer Support

We use a chat-first approach to keep technical communication secure, structured and centralised.

To contact API & Developer Support:

1. Open the Bigmedia24 chat in the bottom-right corner of the website.
2. Start your message with “API support” or “Developer support”.
3. Tell us who you are (hotel IT, partner, OTA, tech provider, developer, etc.).
4. Briefly describe your integration, system and current question or issue.

Our team will respond in chat and, if needed, create or link a ticket in our Support Portal so we can track the case, involve the right specialists and share updates clearly.

API & Developer Support focuses on all topics related to connectivity and integrations between your systems and Bigmedia24, including:

• access to API environments (sandbox and production)
• authentication concepts and token handling
• endpoint usage, request/response formats and error codes
• data mapping (hotels, units, rate plans, reservations, content)
• performance and rate-limiting considerations
• best practices for monitoring and incident handling

We work closely with Technical Support, so your request is handled by the right combination of teams depending on whether your question is primarily about integration, configuration or system behaviour.

Our API & Developer Support is designed for:

• hotel technology providers (PMS, CRS, channel managers, booking engines, CRM, revenue tools)
• OTAs, distributors and travel companies integrating with Bigmedia24 or the BM24 Travel Network
• internal IT and digital teams at hotels and hotel groups
• developers building custom tools or applications on top of Bigmedia24 data and services

If you are not sure whether your question is “technical enough” for this team, just start in chat. We will route you to the appropriate support channel.

Bigmedia24 APIs are designed with separate environments and secure authentication mechanisms to protect data and ensure stability.

Environments

• Sandbox – used for development, testing and QA with non-live data
• Production – used for live traffic and real hotel, availability, rate and reservation data

Most integrations begin in the sandbox environment and move to production after successful testing and a joint review.

Authentication

Our APIs use secure authentication mechanisms (such as API keys or token-based access) to control which clients can access which endpoints and data. Exact details, including headers, token lifetimes and scopes, are documented in the full technical reference you receive once access is granted.

If you are unsure about how to authenticate, include the environment, the endpoint and any error codes in your chat message so we can help you quickly.

Common questions and use cases handled by API & Developer Support include:

• setting up initial API access for sandbox testing
• validating request formats and payload structures
• interpreting error responses, timeouts or unexpected data
• aligning identifiers and mappings between your system and Bigmedia24
• optimising integration patterns to respect rate limits and avoid unnecessary calls
• preparing a production go-live from a technical perspective

To help us support you efficiently, please include as much of the following information as possible when you contact us:

• your organisation and role (e.g. OTA developer, PMS integrator, hotel IT)
• the system or platform you are connecting (name and version, if relevant)
• environment (sandbox or production)
• the endpoint(s) or functional area you are working with
• timestamp(s) of problematic calls, including time zone
• example request and response (sanitised if needed)
• error codes or messages you are receiving

You can paste relevant snippets directly into the chat. If we need full logs or larger payload examples, we will coordinate how best to share them securely.

API & Developer Support works closely with our Technical Support team and uses the same secure Support Portal and Ticket System.

• API-specific questions are handled by the developer support team.
• Broader technical issues (e.g. UI behaviour, configuration) may involve Technical Support.
• For longer-running or complex topics, we create a ticket in the Support Portal so that progress, changes and decisions are properly documented.

You do not need to choose the team yourself – simply start in chat, and we will route your request internally to the appropriate specialists.

Based on our experience with hotel, OTA and technology partners, we recommend the following best practices when integrating with Bigmedia24 APIs:

• Start small – focus first on the core endpoints needed for your initial use case.
• Use sandbox extensively – test key flows and edge cases before requesting production access.
• Implement robust error handling – include retries where appropriate and log errors with enough context.
• Respect rate limits – avoid unnecessary polling and design your integration to handle usage limits gracefully.
• Keep mappings clean – maintain clear mappings for hotels, units, rate plans and other identifiers.
• Communicate early – inform us in advance about major changes or traffic spikes so we can support them.

Security and data protection are central to how we design and operate our APIs and support processes. Our chat-first and portal-based approach helps keep sensitive technical information inside a controlled environment instead of scattered across email inboxes.

Please avoid sending credentials or highly sensitive data in plain text. If we need specific access details for troubleshooting, we will coordinate the safest way to provide them within our established processes.

For legal and formal correspondence, you can reach us at:

Bigmedia24 Dynamics Ltd.
51 Bracken Road
Sandyford, D18 CV48
Dublin, Ireland

Phone (Ireland): +353 1 578 8066
Phone (USA): +1 306 261 9933
Email (legal use): support@bigmedia24.com
Website: https://bigmedia24.com

For operational API & developer topics, please use the chat (bottom-right) and, where applicable, our Support Portal instead of email.