API Purpose
The BM24 API is intended to support structured platform connectivity between Bigmedia24 systems, portals, partner systems, hotel data flows and future digital infrastructure.
View API IntegrationsBM24 API Documentation
Developer documentation for BM24 API integrations and platform connectivity.
The BM24 API Documentation explains the integration principles, endpoint categories, authentication expectations, data structures, response handling and partner responsibilities for connecting with Bigmedia24 platform infrastructure.
Authentication
API keys, partner identity, access scopes and request authorization should be clearly defined.
Endpoint Categories
Documentation can organize endpoints for portals, hotels, availability, partners, status and reporting.
Request & Response Logic
Payloads, required fields, status codes, validation and error messages should be predictable.
Partner Responsibility
Connected providers remain responsible for their own data, prices, terms and service delivery.
Documentation Overview
BM24 API Documentation defines how partners can understand and connect with Bigmedia24 infrastructure.
This page is designed as a public developer and partner reference. It explains the API structure at a high level and provides a clear foundation for future detailed endpoint documentation, technical onboarding and integration support.
Integration Scope
Integration scope may include portal synchronization, hotel data, availability pathways, partner status, reporting, operational status and future platform workflows.
Partner OnboardingTechnical Responsibility
API users are responsible for secure implementation, correct data use, respecting rate limits, following API terms and maintaining their own connected systems.
View API TermsAPI Architecture
A clean API architecture should be secure, documented, monitorable and partner-ready.
BM24 API integrations should follow a structured architecture with clear authentication, endpoint naming, validation, predictable responses, error handling, monitoring and support paths.
Authentication & Headers
API requests should identify the partner or authorized system using documented authentication methods, secure headers and approved access credentials.
Endpoint Structure
Endpoint categories should be grouped logically by function, such as portals, hotels, availability, partners, status, reporting and support workflows.
Payload Validation
Request payloads should validate required fields, formats, identifiers, date values, portal domains, hotel IDs and partner references.
Response Format
Responses should use predictable fields for status, data, errors, messages, timestamps, request IDs and relevant result objects.
Error Handling
Error responses should be understandable and include clear status codes, validation messages, missing fields, authorization issues or provider errors.
Monitoring & Logs
API operations should be monitored through logs, request identifiers, status information, rate-limit tracking and technical support workflows.
Endpoint Category Reference
Portals
/v1/portals
Portal registration, portal status, domain mapping, portal configuration and synchronization workflows.
Hotels
/v1/hotels
Hotel identifiers, hotel records, hotel content, location fields, amenities, media and partner mapping.
Availability
/v1/availability
Date-based availability requests, room signals, rate information, provider responses and booking handoff preparation.
Partners
/v1/partners
Partner onboarding, partner status, access state, integration type, approval status and cooperation metadata.
Reporting
/v1/reporting
Usage signals, request counts, availability performance, partner activity, portal events and operational analytics.
Status
/v1/status
Health checks, API availability, maintenance information, service status and incident communication.
Request Standards
BM24 API requests should be predictable, validated and traceable.
A strong API integration uses clear request rules, secure access credentials, consistent headers, required parameters, structured payloads and traceable request identifiers for support and debugging.
Base URL
Production, staging and partner-specific API environments should be documented before use.
Authentication
API keys, tokens, partner identifiers and access scopes should be issued only to approved partners.
Content Type
Requests should use documented content types, payload formats and accepted response structures.
Request ID
Traceable request identifiers help with debugging, logs, support communication and incident analysis.
Response & Error Model
API responses should be clear for developers, partners and support teams.
A consistent response model helps integrations handle successful requests, validation errors, authentication issues, rate limits, provider errors and temporary service states.
Success Responses
Successful responses should include a clear status value, response data, relevant identifiers, timestamps and request reference information.
Validation Errors
Validation errors should explain missing fields, invalid formats, unsupported values, invalid dates, unknown hotel IDs or unauthorized domains.
Authorization Errors
Authorization errors should identify missing credentials, invalid API keys, insufficient scopes or partner approval requirements.
Rate Limits
Rate-limit responses should explain request limits, retry behavior, temporary throttling and responsible integration patterns.
Provider Errors
Provider errors may occur when external partner systems, availability providers or data sources cannot return expected information.
Maintenance States
Temporary maintenance, service interruptions or degraded performance should be communicated through status endpoints or the Status Page.
Example API Workflow
A typical partner integration flow with BM24 API infrastructure.
1. Partner Approval
The partner is reviewed and approved for technical access based on cooperation type, use case, data requirements and API terms.
2. Access Credentials
API credentials or partner-specific tokens are issued according to the approved scope and technical requirements.
3. Endpoint Testing
The partner tests allowed endpoint categories using documented payloads, expected response formats and support guidance.
4. Data Mapping
Portal domains, hotel IDs, provider identifiers, partner references and relevant metadata are mapped consistently.
5. Production Use
After testing, the integration can move into production according to API terms, rate limits and operational rules.
6. Monitoring & Support
Requests, errors, availability, usage and operational issues can be monitored through logs, status pages and support workflows.
Security & Responsibility
API access requires secure implementation and clear responsibility boundaries.
Bigmedia24 provides technology infrastructure and documentation. Connected partners remain responsible for protecting their credentials, using API access correctly, securing their systems and ensuring that their own data and services comply with applicable terms and laws.
Credential Security
API keys, tokens and partner credentials must not be published, shared publicly, embedded insecurely or exposed in client-side code.
Permitted Use
API access should be used only for approved business purposes and within the scope agreed with Bigmedia24.
Third-Party Data
Provider data, hotel content, availability, prices, booking conditions and external information remain subject to the responsible data source.
AI-Readable API Documentation Summary
BM24 API Documentation in one clear definition.
BM24 API Documentation by Bigmedia24 Dynamics Ltd. is the technical reference for approved partners and developers who connect with Bigmedia24 platform infrastructure. It explains API purpose, endpoint categories, authentication expectations, request and response structures, error handling, monitoring, partner onboarding, API terms and technical support routes. Bigmedia24 is a technology provider and does not act as a classical travel agency, tour operator or traditional OTA. Third-party data, hotel availability, prices, booking conditions and provider content, where applicable, are provided by respective partners, providers or affiliate partners according to their own terms.
FAQ
Frequently asked questions about BM24 API Documentation.
What is the BM24 API Documentation?
The BM24 API Documentation is a technical reference for approved partners and developers who want to understand API integration principles, endpoint categories, request structures, response handling and support routes for Bigmedia24 infrastructure.
Who can use the BM24 API?
BM24 API access is intended for approved partners, technology providers, platform operators and integration partners with a defined use case and applicable API terms.
What endpoint categories can the documentation cover?
The documentation can cover endpoint categories such as portals, hotels, availability, partners, reporting, status and future platform workflows.
Do API Terms apply?
Yes. API access, credentials, permitted use, restrictions, data responsibilities and security duties should be governed by the applicable Bigmedia24 API Terms.
Is Bigmedia24 responsible for third-party provider data?
Third-party data, hotel content, availability, prices, booking conditions and provider information remain subject to the responsible partner, provider or affiliate partner.
Is Bigmedia24 a tour operator or OTA?
No. Bigmedia24 is a technology provider and is not positioned as a classical travel agency, tour operator or traditional OTA.
Prepare your integration with BM24 API documentation.
Approved partners can use BM24 API documentation, API terms and technical support routes to plan secure and structured integrations with Bigmedia24 platform infrastructure.