How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cabify

Cabify Journeys API

This section covers the mobility solution for all companies looking to transport their employees in a simple, safe and comfortable way. We offer different types of vehicles with private drivers and provide everything you need to enjoy your journey, such as a good driver and a top-of-the-range car.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cabify Journeys API is one of 13 APIs that Cabify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Journeys. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and a changelog.

This API exposes 5 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 4.0.

Requests are made against 2 base URLs: https://cabify.com, https://cabify-sandbox.com.

5 operations 4 paths 23 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0
Base URL
https://cabify.com/api/v4
Authentication
HTTP Bearer
Contact
ridehailing.api@cabify.support
License
Cabify Api support
Resource Areas
1

Authentication & Security 1

Cabify Journeys API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (access_token). By default, every request must be authenticated.

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Journeys 5

This section covers the mobility solution for all companies looking to transport their employees in a simple, safe and comfortable way. We offer different types of vehicles with p…

POST
/api/v4/journey/{id}/state
Cancel Journey
cancelJourney 1 param → 200400401409500
GET
/api/v4/journey/{id}/state
Get Journey State
getJourneyState 2 params → 200400401404500
POST
/api/v4/journey
Create a journey
createJourney body → 200400401404500
GET
/api/v4/journey/{journey_id}
Get Journey details
getJourney 1 param → 200400401500
POST
/api/v4/journey/{id}/keep_searching
Keep searching drivers for a journey
keepSearching 1 param → 204400401404500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are Journey (15 properties), StopResponse (13 properties), StopRequest (12 properties), JourneyRequest (9 properties). Each schema is shown below with its type and property counts.

UnauthorizedRequest
object
The token used is invalid either because it is expired or because it is incorrect.
1 property
JourneyRequest
object
Input object needed to create a new journey. ⚠️ Always estimate before creating a journey You must call /estimates before creating a journey. The estimation re…
9 properties 4 required
Totals
objectnull
Price breakdown for the journey. Only populated after the journey reaches terminated state.
3 properties
StopResponse
object
Stop of a journey. A journey needs to have at least 2 stops: the first one is considered the pickup point the last one the destination.
13 properties 1 required
Mobile
object
Input Mobile Number. Required when the rider is external. Journey's SMS state updates will arrive to this mobile.
2 properties 2 required
Journey
object
Booking-level details of a journey including stops, pricing, timestamps, and lifecycle status.
15 properties 1 required
JourneyResponse
object
1 property
JourneyState
object
Real-time operational state of an active journey: the assigned driver, their vehicle, and the route waypoints recorded so far.
7 properties
Vehicle
object
Journey's vehicle information.
3 properties
Row
object
Point and state through which the driver passed during the journey.
2 properties
NotFound
object
The server did not find a current representation for the target resource
1 property
Rider
object
Input data defining the rider of a journey.
5 properties
StopRequest
object
Stop of a journey. A journey needs to have at least 2 stops: the first one is considered the pickup point the last one the destination.
12 properties 1 required
Price
object
Price in the currency smallest unit.
2 properties
InternalServerError
object
indicates that an internal server error occurred
1 property
Driver
object
Driver's information.
4 properties
Contact
object
Contact details on each Stop. Include this object if you want the Driver to see additional Contact details on each Stop.
4 properties
Waypoint
object
Information about the different points through which the driver passed during the journey.
2 properties
BadRequest
object
Indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax…
1 property
MeetingPoint
object
A specific meeting point within a hub location (e.g. a terminal at an airport). Obtained from the hub data returned in the estimates response.
3 properties 3 required
DriverStopBeforePickup
objectnull
Best-effort location where the driver is heading before coming to the pickup. May be null even when isdriveronanotherjourney is true.
1 property
PreassignedDriver
objectnull
Driver preassigned to the journey (for example on a reservation) before the journey is actually assigned. It does not include the phone number, and it may chan…
3 properties
Conflict
object
The request conflicts with the current state of the resource. For journey cancellation, this means the journey has already been cancelled, terminated, or is in…
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cabify-journeys-api-openapi.yml Raw ↑

Other APIs Cabify publishes across the network.

Cabify delivery API
AE Profile APIs.io
Cabify Estimates API
AE Profile APIs.io
Cabify hubs API
AE Profile APIs.io
Cabify label API
AE Profile APIs.io
Cabify Labels API
AE Profile APIs.io
Cabify parcels API
AE Profile APIs.io
Cabify Sales API
AE Profile APIs.io
Cabify shipment API
AE Profile APIs.io
Cabify shipping_types API
AE Profile APIs.io
Cabify status API
AE Profile APIs.io
Cabify users API
AE Profile APIs.io
Cabify webhooks API
AE Profile APIs.io
#Journeys
← Back to C APIs
API Details
ID
cabify:cabify-journeys-api
Base URL
https://cabify.com/api/v4
Docs
https://developers.cabify.com/docs/ride-hailing
Provider
Cabify
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cabify-journeys-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cabify-journeys-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cabify Journeys API, 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.