Clickbus
Use ClickBus data APIs through OpenAny to search bus trips, compare listed fares and inspect operators, stations, routes and itineraries. For bus company, supply record slug in the query. Other available operations include destination page, trip itinerary, nearest low-fare date, route page, bus station. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. Each API page provides supported parameters, request and response examples, and usage pricing.
- Endpoints
- 9In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
ClickBus station list API
Use the ClickBus station list API to retrieve station records, regional records, record identities and titles and source-page links as structured JSON from ClickBus. Choose search words as optional query conditions to select the source records or view required for your request. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. Continue with the returned next_page as page; a null value marks the last page. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus place autocomplete API
Use the ClickBus place autocomplete API to retrieve place records, calculated distance, geographic coordinates, record identities and titles and geographic references as structured JSON from ClickBus. Choose search words, coordinates and longitude as optional query conditions to select the source records or view required for your request. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus nearest low-fare date API
Use the ClickBus nearest low-fare date API to retrieve lowest-fare date as structured JSON from ClickBus. Supply origin identifier and destination identifier in the query; optionally select date and departure offset in days to set the requested scope. Use these results to compare the lowest displayed fares across dates before choosing a date for detailed travel searches. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus route page API
Use the ClickBus route page API to retrieve transport operators, source-page links and record identities and titles as structured JSON from ClickBus. Supply origin and destination in the query. Use these results to compare journey options for the selected route and dates before choosing a travel itinerary. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus trip itinerary API
Use the ClickBus trip itinerary API to retrieve preparation steps, duration information, journey segments and endpoints and station and stop records as structured JSON from ClickBus. Choose origin, destination and departure offset in days as optional query conditions to select the source records or view required for your request. Use these results to compare journey options for the selected route and dates before choosing a travel itinerary. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus destination page API
Use the ClickBus destination page API to retrieve price information, available offers, place matches, transport operators, source-page links and record identities and titles as structured JSON from ClickBus. Supply city in the query. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus bus station API
Use the ClickBus bus station API to retrieve geographic coordinates, service options, transport operators, record identities and titles and source-page links as structured JSON from ClickBus. Supply record slug in the query. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus bus trips API
Use the ClickBus bus trips API to retrieve trip options, price information, product records, transport operators, filter and option values and duration information as structured JSON from ClickBus. Supply origin and destination in the query; optionally select date, departure offset in days and travel date to set the requested scope. Use these results to compare journey options for the selected route and dates before choosing a travel itinerary. For sort option, choose departure / price / duration / arrival. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
ClickBus bus company API
Use the ClickBus bus company API to retrieve section structure, movement information, published text, source-page links and record identities and titles as structured JSON from ClickBus. Supply record slug in the query. Use these results to reconcile transport-location identifiers and connect stations or cities with published services. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.
Common questions
How are Clickbus APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Clickbus requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Clickbus with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.