Elkanio Synapse: the unified travel API the whole platform runs on
Stop building brittle point-to-point connections. Synapse provides a single, universally mapped REST interface to airlines (GDS, NDC and LCC), hotels, activities, insurance, visa, cab, bus, ferry and cruise, kept working by an agentic runtime that heals supplier schema changes before they break a booking.
Death by a thousand integrations
Maintaining supplier connections natively means engineers handling disparate XML and JSON structures, undocumented changes and latency for every airline, bedbank and operator. Each new vertical multiplies the problem.
The orchestration layer
Synapse ingests supplier endpoints and outputs one predictable schema across every vertical. When suppliers push unannounced changes, the agentic runtime proposes a mapping patch, replays real traffic against it and promotes it, then tells an engineer what it did.
What Synapse does.
Single-schema normalisation
One REST API. LCC feeds, GDS EDIFACT, NDC and bedbank structures come back as one predictable JSON response. Build your front-end logic once.
Sub-second, price-honest search
Distributed Redis clusters return availability quickly while a refresh strategy keeps cached prices matched to what the supplier will confirm.
Intelligent supplier selection
Synapse ranks suppliers per route by live latency and success rate, so search goes only where an answer is likely, lowering look-to-book cost.
Self-healing integrations
Schema drift is detected, a mapping patch is proposed, replayed against recorded traffic and promoted behind a versioned mapping with rollback. Engineers see every change in the audit log.
One order model & webhooks
Create, change, cancel and refund through the same order model in every vertical. Webhooks for order, ticketing, policy issuance and payment events fire the moment they happen.
Sandbox, keys & observability
A sandbox with production parity, per-key rate limits, idempotency keys, request logs and supplier health per route. OpenAPI 3 schema, Postman collections and typed clients.
From setup to steady state.
- 1
Get keys and a sandbox
Same mappings and agents as production, with simulated supplier responses.
- 2
Search across verticals
One request can span flights, hotels, insurance and ground. Components come back typed and normalised.
- 3
Book through one order model
Create the order, take payment, receive tickets and vouchers, all in the same shapes.
- 4
Operate
Webhooks drive your systems, health per supplier drives routing and agents heal drift while you sleep.
99.99% SLA-backed uptime
Contractual, for the gateway and the portals that run on it. Multi-region deployment with data residency in India, Singapore, EU & Dubai.
Sandbox with parity
Same mappings, same agents, simulated supplier responses. Postman collections and typed client libraries.
Granular webhooks
Order, ticketing, policy issuance and payment events pushed the moment they happen.
Nine verticals, one request, one response.
A search can span flights, hotels, insurance and ground in a single call. Components come back typed and normalised, whatever the source system, and every order emits the same webhook stream.
// Illustrative request shape — one call, several verticals
POST /v2/offers/search
{
"trip": { "from": "COK", "to": "DXB", "depart": "2026-11-04", "return": "2026-11-11" },
"pax": { "adt": 2, "chd": 1 },
"include": ["flights", "hotels", "insurance", "cab"]
}// One normalised response, whatever the source system
200 OK
{
"offers": [{
"id": "of_…",
"components": [
{ "type": "flight", "source": "ndc|gds|lcc" },
{ "type": "hotel", "source": "bedbank|direct" },
{ "type": "insurance", "source": "insurer" },
{ "type": "cab", "source": "transfer-operator" }
],
"total": { "currency": "INR", "amount": "…" }
}],
"webhooks": ["order.created", "ticket.issued", "policy.issued"]
}Field names shown are representative of the v2 schema; the sandbox returns the authoritative OpenAPI definition.
Where Synapse fits.
Synapse is part of these solution packages. Each combines a few products for one kind of travel business or one business need.
One of 12 products on a single core.
Synapse shares its data model, supplier connectivity and customer records with every other Elkanio product. Start with one, add the next without an integration project.
See the full platformQuestions about Synapse.
What is Elkanio Synapse?
Synapse is a unified travel API. It normalises airlines (GDS, NDC and LCC), hotels, activities, insurance, visa, cab, bus, ferry and cruise supply into one REST API with a single schema.
What does “agentic self-healing” mean in Synapse?
When a supplier changes its response format, a supervised agent detects the drift, proposes a mapping patch, replays cached real traffic against it and promotes the fix behind a versioned mapping with rollback. Engineers are notified of every change.
Is there a sandbox?
Yes. The sandbox uses the same mappings and agents as production with simulated supplier responses, so integrations can be built and tested before go-live.
Is Synapse REST or GraphQL?
REST, described by a published OpenAPI 3 schema, with JSON responses, webhooks for order events, per-key rate limits and idempotency keys.
Can we use Synapse without the other Elkanio products?
Yes. Synapse is sold on its own for teams building their own front ends. Every other Elkanio product also runs on it, so adding Nucleus, Nova or Vector later needs no new integration.
Ready to re-architect your booking flow?
Stop burning engineering cycles on supplier maintenance. Bring a technical lead; we will walk your team through the schema, the agents and your migration path.