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 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.

Documentation Provider Profile APIs.io OpenAPI GitHub

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.2.0, at version 1.0.0.

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

11 operations 7 paths 20 schemas 5 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://cabify.com/api/v4
Authentication
HTTP Bearer
Contact
p.delivery@cabify.com
Resource Areas
1

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.

parcels 11

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…

POST
/v1/parcels
Create new parcels.
addParcels body → 200400401409422
GET
/v1/parcels
List parcels filtered by state.
getParcels 2 params → 200400401
POST
/v1/parcels/{parcel_id}/proof_configuration
Set proof of delivery configuration for a parcel.
createProofConfigurationParcel 1 param body → 200401404
GET
/v1/parcels/{parcel_id}/proof_configuration
Get proof of delivery configuration for a parcel.
proofConfigurationParcel 1 param → 200401404
POST
/v1/parcels/delete
Delete parcels by ID.
deleteParcels body → 202401404
GET
/v1/parcels/{parcel_id}
Get a parcel by ID.
getParcel 1 param → 200401404
PUT
/v1/parcels/{parcel_id}
Update a parcel by ID.
updateParcel 1 param body → 200400401403409422
GET
/v1/parcels/{parcel_id}/tip
Get the tip for a parcel.
getTipParcel 1 param → 200204401403404
POST
/v1/parcels/{parcel_id}/tip
Add a tip for a parcel delivery.
tipParcel 1 param body → 200401403404409429
GET
/v1/parcels/{parcel_id}/label
Get the shipping label for a parcel.
labelParcel 1 param → 200401403404
POST
/v1/parcels/{parcel_id}/notify
Notify an event for the given parcel.
notifyParcel 1 param body → 202400403404409422500

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.

DeleteParcels
object
1 property 1 required
ParcelWeight
object
Weight of the parcel.
2 properties
RequestError
object
Standard error response body returned when a request fails.
1 property 1 required
NewParcels
object
1 property 1 required
ParcelDimensions
object
Physical dimensions of the parcel.
4 properties
Tip
object
3 properties
Parcel
object
9 properties
Parcels
object
1 property 1 required
CreateProofConfiguration
object
Request body for creating or replacing proof of delivery configuration for a parcel.
1 property
PaginatedParcels
object
4 properties 4 required
UpdateParcel
object
Fields that can be updated on an existing parcel. Only fields included in the request will be modified.
8 properties
NewParcelPickupContact
object
2 properties
Price
object
Price information for the parcel, used in cash-on-delivery scenarios.
3 properties
ProofConfiguration
object
The proof of delivery methods configured for a parcel.
2 properties 2 required
Point
object
A geographic coordinate expressed as latitude and longitude.
2 properties 2 required
ParcelPointPickupInfo
object
Information about the pickup point. You must provide exactly one of the following location fields: loc (coordinates), addr (address string), or hubexternalid (…
6 properties 1 required
ParcelPointDropoffInfo
object
Information about the drop-off (destination) point. You must provide exactly one of the following location fields: loc (coordinates), addr (address string), or…
5 properties 1 required
NewParcel
object
8 properties 2 required
NewParcelDropoffContact
object
2 properties
CreateTip
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cabify-parcels-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 Journeys API
AE Profile APIs.io
Cabify label API
AE Profile APIs.io
Cabify Labels 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
#Parcels
← Back to C APIs
API Details
ID
cabify:cabify-parcels-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-parcels-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cabify-parcels-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 parcels 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.