WebAdmin
One environment for bookings, suppliers, clients, pricing, credit, tasks, finance and reporting.
Explore WebAdmin- Bookings
- Clients
- Credit
- Reporting
BLACKROCK CONNECT · API DISTRIBUTIONTurn your supply
Turn your supply
into a platform.
For travel businesses in the GCC that hold supplier relationships, contracts or aggregated content. Blackrock API distribution exposes approved inventory to travel agencies, affiliates, wholesalers and other connected partners through APIs built around real-time search, booking and operational requirements, with limits, pricing and access set for each customer.
Also see: Blackrock B2B · WebAdmin
250+ integrations across the travel ecosystem
- Amadeus
- Expedia
- Hotelbeds
- TravelgateX
- WebBeds
- RateHawk
- TBO
- flydubai
ROUTE TO MARKET
From buyer to seller.
Once you have supplier relationships, contracts or aggregated content, API distribution can create an additional route to market. Blackrock can expose approved inventory to travel agencies, affiliates, wholesalers or other connected partners.
Your supply
- Supplier relationships
- Your own contracts
- Aggregated content
API distribution
Approved inventory through managed APIs, with controls for each customer.
Downstream customers
- Travel agencies
- Affiliates
- Wholesalers
- Connected partners
CORE WORKFLOWS
The workflows behind the endpoints.
Depending on product and connection model, APIs can support the workflows below. The examples use fictional data.
Real-time search and availability
A partner sends a search and receives availability for the inventory you have approved for it.
- Static content
- Mapping references
- Product and supplier access, set for each client
// POST /v1/hotels/search
{
"client_ref": "SRCH-3021",
"destination": "Dubai, AE",
"check_in": "18 Oct",
"nights": 5,
"adults": 2,
"child_ages": [6, 9],
"currency": "AED"
}// 200 OK
{
"search_id": "sr-4d81",
"results": [
{
"hotel_id": "LCH-5718",
"name": "Lantern Cove Hotel",
"area": "Dubai Marina",
"board": "Room only",
"free_cancel_until": "12 Oct",
"rate_token": "rt-9c27e1",
"total": 4644.00,
"currency": "AED"
}
// more results follow
]
}Illustrative example with fictional data, not a live endpoint.
Confirm the rate before you book
Where the supplier workflow requires it, rate and availability are reconfirmed before the booking is committed. That manages the gap between the search response and final confirmation.
- Rate or quote check
- Prices follow each client's pricing rules
// POST /v1/hotels/rates/check
{
"rate_token": "rt-9c27e1"
}// 200 OK
{
"rate_token": "rt-9c27e1",
"available": true,
"price_changed": false,
"total": 4644.00,
"currency": "AED",
"free_cancel_until": "12 Oct"
}Illustrative example with fictional data, not a live endpoint.
Book, retrieve and cancel
Once the rate is confirmed, the partner books, then retrieves or cancels the booking as needed. Account and client references are supported alongside.
- Booking
- Booking retrieval
- Cancellation
- Account and client references
// POST /v1/bookings
{
"rate_token": "rt-9c27e1",
"client_ref": "OAK-88214",
"lead_guest": "Layla Ahmed",
"payment": "on_account"
}// 201 Created
{
"booking_id": "BK-46913",
"status": "confirmed",
"client_ref": "OAK-88214",
"total": 4644.00,
"currency": "AED"
}Illustrative example with fictional data, not a live endpoint.
CLIENT CONTROLS
Different customers, different rules.
Different downstream customers can have different commercial and operational rules, so each client gets its own settings.
- Credentials for each client
- Client-level rate limits
- IP controls
- Pricing rules and credit handling
- Product and supplier access
Ready to turn your supply into a platform?
See API distribution on your suppliers and your customers, in a walkthrough with the right team.
OBSERVABILITY
See how customers use your platform.
See how customers and integrations are using the platform, with logs and usage reporting by client and by supplier.
- Search volume
- Response time
- Error rate
- Bookings
- Conversion
- Client usage
- Supplier usage
- Request logs
DESIGNED FOR TRAFFIC
Designed for traffic.
API distribution can generate extremely high search volume compared with direct user channels. Blackrock architectures can include rate limiting, caching, asynchronous processing, queueing, monitoring and client-specific controls to keep the platform predictable under load.
- Partner requests
Search volume can far exceed direct user channels.
- 01Client controls
Credentials, IP controls and client-specific rules.
- 02Rate limiting
Limits set at client level.
- 03Caching
Results kept ready for repeated searches.
- 04Queues and async processing
Bursts and slower work are queued and processed asynchronously.
- Supplier connections
Your own contracts and aggregated content, behind one connectivity layer.
- Monitoring
Search volume, response time and error rate, by client and by supplier.
Illustrative. The exact design depends on the product and connection model.
BEYOND THE ENDPOINT
Build a distribution business, not just an endpoint.
API distribution is connected to WebAdmin, finance and client management, so commercial relationships can be operated beyond the technical connection.
Finance
API distribution is connected to finance, with credit handling for each client. Blackrock is a TRAACS certified integration partner for integrated travel accounting.
Explore Finance- Credit handling
- Statements
- Invoices
Client management
Every downstream customer is a client with its own pricing, credit and access, managed alongside the rest of your accounts.
Explore Blackrock B2B- Accounts
- Pricing rules
- Access
HOW YOU GO LIVE
From your supply to a live API.
A hybrid model: configure the platform yourself, while our engineers handle everything specific to your business.
- 01
Choose what to expose
Decide which approved inventory, products and suppliers each downstream customer can see.
- 02
Set each customer's rules
Issue credentials, then set rate limits, IP controls, pricing rules and credit for every client.
- 03
Connect the partner
The customer integrates against search, rate check, booking, retrieval and cancellation.
- 04
Operate it
Follow logs and usage reporting, with WebAdmin, finance and client management alongside.
Go live in 2–6 weeks. Timelines vary with scope, suppliers and custom work.
QUESTIONS
Questions about API distribution
Which workflows does the API cover?
Depending on product and connection model, APIs can support search and availability, rate or quote check, booking, booking retrieval, cancellation, static content, mapping references, and account or client references.
Can each customer have its own prices and access?
Yes. Different downstream customers can have different commercial and operational rules. Support can include credentials, client-level rate limits, IP controls, pricing rules, credit handling, and product and supplier access.
Can I distribute my own contracts as well as aggregated content?
Yes. Once you have supplier relationships, contracts or aggregated content, Blackrock can expose approved inventory to travel agencies, affiliates, wholesalers or other connected partners. Blackrock has 200+ supplier connections.
What happens when a partner sends heavy search traffic?
API distribution can generate extremely high search volume compared with direct user channels, so Blackrock architectures can include rate limiting, caching, asynchronous processing, queueing, monitoring and client-specific controls to keep the platform predictable under load.
How do I see what my customers and integrations are doing?
Through logs and usage reporting, with observability of search volume, response time, error rate, bookings, conversion, client usage and supplier usage.
How long does it take to go live, and what support is there?
Delivery is hybrid: you configure the platform yourself while our engineers handle everything specific to your business, and you can go live in 2–6 weeks. Timelines vary with scope, suppliers and custom work. Support is 24/7 and local.