Traveloka
Traveloka (Traveloka Services Pte. Ltd.) is a Southeast Asian multi-product online travel agency operating across Indonesia, Thailand, Vietnam, Malaysia, Singapore, the Philippines, Australia, Japan and South Korea, selling flights, hotels and alternative stays, activities (Xperience), trains, cruises, buses, car rental and airport transfers. Its API surface is entirely partner-facing and runs in three distinct programs: the Traveloka Partners Network (LOKA) v2 REST API for distribution partners reselling Traveloka accommodation inventory; Traveloka Connect, an OpenTravel (OTA) 2017B XML connectivity API for channel managers and property-management systems pushing availability, rates and content; and Traveloka Atlas, a published JSON specification that accommodation suppliers implement on their own hosts so Traveloka can search and book against them. All three are approval-gated behind a partnership agreement and certification; none offer self-serve signup.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Traveloka the way a machine reads it — 36 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Traveloka scores 50.3/100 (developing), with a separate agent-readiness read of 55/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Traveloka's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/traveloka/"
title="Traveloka on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/traveloka.svg"
alt="Traveloka Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/traveloka/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/traveloka/"
title="Traveloka on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/traveloka/card.svg"
alt="Traveloka Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Traveloka
Each block below is one kind of artifact we hold for Traveloka. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Traveloka Connect - Connectivity API
OpenTravel (OTA) 2017B XML connectivity API for channel managers, property-management systems and hotel technology partners. Traveloka hosts the ARI (availability, rates, invent...
Traveloka 1.1 Content - Hotel & Room API
The 1.1 Content - Hotel & Room API from Traveloka — 2 operation(s) for 1.1 content - hotel & room.
Traveloka 2.1 Search - HotelList API
The 2.1 Search - HotelList API from Traveloka — 1 operation(s) for 2.1 search - hotellist.
Traveloka 2.2 Search - RoomList API
The 2.2 Search - RoomList API from Traveloka — 1 operation(s) for 2.2 search - roomlist.
Traveloka 2.3 Search - BulkRoomList API
The 2.3 Search - BulkRoomList API from Traveloka — 1 operation(s) for 2.3 search - bulkroomlist.
Traveloka 3.1 Booking - Book API
The 3.1 Booking - Book API from Traveloka — 1 operation(s) for 3.1 booking - book.
Traveloka 3.2 Booking - IssueCheck API
The 3.2 Booking - IssueCheck API from Traveloka — 1 operation(s) for 3.2 booking - issuecheck.
Traveloka 3.3 Booking - Issue API
The 3.3 Booking - Issue API from Traveloka — 1 operation(s) for 3.3 booking - issue.
Traveloka 3.4 Booking - BookingSummary API
The 3.4 Booking - BookingSummary API from Traveloka — 1 operation(s) for 3.4 booking - bookingsummary.
Traveloka 3.5 Booking - Cancel API
The 3.5 Booking - Cancel API from Traveloka — 1 operation(s) for 3.5 booking - cancel.
Traveloka Authorization API
The Authorization API from Traveloka — 1 operation(s) for authorization.
Traveloka Booking API
The Booking API from Traveloka — 4 operation(s) for booking.
Traveloka Content API
The Content API from Traveloka — 2 operation(s) for content.
Traveloka Discovery (Optional) API
This API is optional and intended for partners who do not have their own master data.
Traveloka Rate API
The Rate API from Traveloka — 2 operation(s) for rate.
Scroll within the panel for all 15 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONTraveloka Atlas 1.1 Content - Hotel & Room API
OPEN COLLECTIONTraveloka Atlas 2.1 Search - HotelList API
OPEN COLLECTIONTraveloka Atlas 2.2 Search - RoomList API
OPEN COLLECTIONTraveloka Atlas 2.3 Search - BulkRoomList API
OPEN COLLECTIONTraveloka Atlas 3.1 Booking - Book API
OPEN COLLECTIONTraveloka Atlas 3.2 Booking - IssueCheck API
OPEN COLLECTIONTraveloka Atlas 3.3 Booking - Issue API
OPEN COLLECTIONTraveloka Atlas 3.4 Booking - BookingSummary API
OPEN COLLECTIONTraveloka Atlas 3.5 Booking - Cancel API
OPEN COLLECTIONLOKA Authorization API
OPEN COLLECTIONLOKA Booking API
OPEN COLLECTIONLOKA Content API
OPEN COLLECTIONLOKA Discovery (Optional) Discovery (Optional) API
OPEN COLLECTIONLOKA Rate API
OPEN COLLECTIONScroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
traveloka-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Traveloka Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Traveloka Connect Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Traveloka — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/traveloka · machine-readable index on apis.io
This is an independent, third-party profile of Traveloka, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.