Cabify Sales API
Sales objects are created once a journey transitions into the terminated state and they are associated with the user who requested the journey (which not necessarily is the rider). The transition to terminated happens automatically after 2 hours in production(10 minutes in sandbox environment). You can request them per user (requester of the journey), the client (all ofyour sales), or journey (all Sales associated to a specific journey which in most cases is just one).
Cabify Sales API is one of 13 APIs that Cabify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Sales. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and a changelog.
This API exposes 3 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.
Requests are made against 2 base URLs: https://logistics.api.cabify.com, https://logistics.api.cabify-sandbox.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Cabify Sales API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearer_token).
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.
Sales objects are created once a journey transitions into the terminated state and they are associated with the user who requested the journey (which not necessarily is the rider)…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are StopResponse (13 properties), TypeObjectSale (9 properties), Expense (5 properties), Sale (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Cabify 12
Other APIs Cabify publishes across the network.