Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cabify hubs API

A hub is a physical location (such as a warehouse or store) where parcels are stored until they are ready to be picked up by a driver. You can reference a hub in pickup or drop-off information using its external ID.

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

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

This API exposes 5 operations across 3 paths, and defines 4 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.

5 operations 3 paths 4 schemas 3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://cabify.com/api/v4
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cabify hubs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer_token).

Paths & Operations 5

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

hubs 5

A hub is a physical location (such as a warehouse or store) where parcels are stored until they are ready to be picked up by a driver. You can reference a hub in pickup or drop-of…

GET
/v1/hubs
List all client hubs.
→ 200
POST
/v1/hubs
Create a new client hub.
body → 200401
GET
/v1/hubs/none/{hub_external_id}
Get a client hub by its external ID.
1 param → 200401404
PUT
/v1/hubs/none/{hub_external_id}
Update a client hub by its external ID.
1 param body → 200401
GET
/api/v4/hub
Get Hub by coordinates
getHub 2 params → 200400401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are HubObject (5 properties), HubResponse (1 property), UnauthorizedRequest (1 property), BadRequest (1 property). Each schema is shown below with its type and property counts.

HubObject
object
A hub is a large venue (e.g. airport, train station) with designated pick-up/drop-off meeting points.
5 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
UnauthorizedRequest
object
The token used is invalid either because it is expired or because it is incorrect.
1 property
HubResponse
object
Hub information for a given set of coordinates. Returns null inside the data field when no hub exists at those coordinates.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cabify-hubs-api-openapi.yml Raw ↑

Other APIs Cabify publishes across the network.

Cabify delivery API
Cabify Estimates API
Cabify Journeys API
Cabify label API
Cabify Labels API
Cabify parcels API
Cabify Sales API
Cabify shipment API
Cabify shipping_types API
Cabify status API
Cabify users API
Cabify webhooks API