Required query
The source product ID and the travel dates define the base query.
API delivery
Put source-specific travel rates into your workflow.
Datasynex APIs use JSON responses and source-specific REST endpoints. Each endpoint defines the required query parameters, supported market context, delivery mode, returned fields, and business errors.
Endpoints are defined per product and per source, and the response contract is agreed with you rather than fixed in advance. Production access uses an issued token and a request signature where required.
Request anatomy
Start with the query. Add only supported context.
Source context
Depending on the product and source: travellers, point of sale, currency, language, and channel.
Delivery mode
Use request-time collection where supported, or retrieve previously collected data for recurring workloads.
Illustrative data shape
Keep the offer and its conditions together.
The hotel examples below show field groups described by the product, not a production endpoint contract. Exact paths, names, and availability are confirmed for each product and source, and the response schema is agreed with you.
hotel/illustrative_request.json
{
"hotel_id": "source_hotel_id",
"check_in": "YYYY-MM-DD",
"check_out": "YYYY-MM-DD",
"occupancy": {
"adults": 2,
"rooms": 1
},
"point_of_sale": "…",
"currency": "…"
}hotel/illustrative_response.json
{
"business_code": "…",
"message": "…",
"available": true,
"collected_at": "…",
"rooms": [{
"room_name": "…",
"bed_type": "…",
"rate_plans": [{
"total_price": "…",
"taxes": "…",
"meal": "…",
"cancellation": "…",
"payment_method": "…"
}]
}]
}Application behavior
Read the data result, not only the HTTP status.
A successful HTTP response is not automatically a successful rate result.
Evaluate the endpoint contract together
Check the business code, message, availability state, returned offers, and collection time. The contract also defines errors for invalid input, missing mappings, unavailable data, source timeouts, and service failures.
Input
Are the product mapping and query parameters valid?
Availability
Did the source return a bookable offer for this context?
Freshness
Is the collection time suitable for your decision?
Comparability
Do tax, inclusion, market, and cancellation conditions align?
Field reference
What comes back, per product.
Every line follows the same principle — the offer, and the conditions attached to it. Availability depends on what the source displays for that request.
Hotel
- Room name and bed type
- Occupancy and room availability
- Displayed, discounted, net, tax, and total prices
- Breakfast or meal inclusion
- Cancellation terms and free-cancellation status
- Payment method
- Promotion labels
- Collection timestamp and source page
Flight
- Itinerary and segments
- Cabin class
- Baggage allowance
- Change and refund conditions
- Price and taxes
Car rental
- Vehicle class
- Pickup and drop-off
- Mileage and insurance terms
- Cancellation terms
- Price and taxes
Activities and tickets
- Ticket or package option
- Date and time slot
- Inclusions
- Cancellation terms
- Price and taxes
Hotel is the most established line, so its field set is published. The other three are described here at the level that holds across sources; the exact names and paths are agreed per source during the pilot.
Service levels
What the endpoint commits to.
Real-time means the source is visited for your request, so the figure below is a collection time, not a cache read. Where that budget does not fit the workflow, the cached endpoint answers from previously collected data instead.
Real-time responseP95 under 60s
Collection success95%+ on supported configurations
ThroughputSized with you per workload
Figures apply to supported configurations. Both are measured against your own query set during the pilot and written into the agreed scope before production.
Error contract
Five things that can come back instead of a rate.
Each endpoint names its own business codes. The classes below are what your integration has to handle in every configuration.
Invalid input
The query is malformed, or a parameter is outside what the source accepts.
Missing mapping
The product has no confirmed identifier on the requested source.
Unavailable data
The source returned no bookable offer for this context. This is an answer, not a failure.
Source timeout
The source did not respond inside the window agreed for the endpoint.
Service failure
Collection failed on our side. Retry semantics are defined per endpoint.
Review a real contract
Start with your product, source, and required fields.
We will validate a representative scope, then confirm the endpoint request, response, error states, and production requirements.