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

Cargomatic Carrier API

Endpoints for Cargomatic Carriers and Drivers

Cargomatic Carrier API is one of 5 APIs that Cargomatic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Carrier. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, https://api-acceptance.cargomatic.com.

4 operations 4 paths 10 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://api.cargomatic.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cargomatic Carrier API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 4

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

Carrier 4

Endpoints for Cargomatic Carriers and Drivers

POST
/shipments/appointment
Updates an existing appointment with a new status, start time, and/or end time. Requires the client to send at least one of new windowStart time, new windowEnd time, or appointmentConfirmed.
updateAppointment body → 200400500
POST
/shipments/accept
Accepts a Shipment
acceptShipment body → 200400500
POST
/carrier/{carrierid}/driver
Creates a new Driver
createDriver 1 param body → 200400500
POST
/shipment/assign
Assigna a Driver to a Shipment
assignDriver body → 200400500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CreateDriverRequest (9 properties), UpdateShipmentRequest (5 properties), AcceptShipmentResponse (4 properties), AssignDriverResponse (2 properties). Each schema is shown below with its type and property counts.

AcceptShipmentRequest
object
1 property
InternalServerErrorResponse
object
1 property
BadRequestResponse
object
1 property
CreateDriverRequest
object
9 properties
AcceptShipmentResponse
object
4 properties
UpdateShipmentRequest
object
5 properties
UpdateShipmentResponse
object
2 properties
AssignDriverRequest
object
2 properties
AssignDriverResponse
object
2 properties
CreateDriverResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cargomatic-carrier-api-openapi.yml Raw ↑

Other APIs Cargomatic publishes across the network.

Cargomatic Authorization API
Cargomatic Document API
Cargomatic Shipper API
Cargomatic Stops API
Where this information came from

This is an independent, third-party profile of Cargomatic Carrier 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.