Cabify parcels API
A parcel is the package you need to ship. Each parcel is identified by a unique ID and contains a pickup point (where the driver collects the package) and a drop-off point (the destination). Parcels must be created before they can be shipped.
Cabify parcels API is one of 13 APIs that Cabify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include parcels. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and a changelog.
This API exposes 11 operations across 7 paths, and defines 20 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 parcels API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearer_token).
Paths & Operations 11
Across 7 paths, the API surfaces 11 operations — 5 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
A parcel is the package you need to ship. Each parcel is identified by a unique ID and contains a pickup point (where the driver collects the package) and a drop-off point (the de…
Schemas 20
The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Parcel (9 properties), NewParcel (8 properties), UpdateParcel (8 properties), ParcelPointPickupInfo (6 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.