# Qargo

**Canonical:** https://apis.io/providers/qargo/  
**Website:** https://www.qargo.com/  
**APIs profiled:** 26

Qargo is an intelligent transport management platform (TMS) for road carriers, freight forwarders and 3PLs, using AI to automate operational and administrative work across planning, execution, tracking and accounting. Qargo publishes a public Qargo TMS API (OpenAPI 3.1, v1.2.0, base https://api.qargo.com) exposing tenant-level integration and operational endpoints for orders, trips, companies, resources, documents, tasks and accounting, plus inbound and outbound webhooks and separate Subcontractor and Customer APIs. Service-to-service authentication uses OAuth2 client-credentials (JWT); webhooks use HTTP Basic. Qargo is a Balderton Capital portfolio company.

## Kin Score — 47.5 / 100 (developing)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 47.5).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 59.9 |
| Governance | 16.7 |
| Contract Governance | 16.7 |
| Operational Transparency | 31.6 |
| Developer Ergonomics | 63.7 |
| Commercial Clarity | 27.6 |
| Access Clarity | 27.6 |

## Agent readiness — 45.3 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | documented |
| MCP Server | documented |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | verified |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | yes |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Self-serve signup — onboarding: self-serve, pricing: unknown, trial: no (confidence: medium).

## APIs (26)

- **Qargo Subcontractor API** — Fleet dispatch and subcontractor-specific endpoints for transportation management.
- **Qargo Customer API** — Customer portal endpoints for order tracking, status monitoring and customer-facing operations.
- **Qargo API / Accounting API** — The API / Accounting API from Qargo — 33 operation(s) for api / accounting.
- **Qargo API / Authentication API** — The API / Authentication API from Qargo — 1 operation(s) for api / authentication.
- **Qargo API / Company API** — The API / Company API from Qargo — 6 operation(s) for api / company.
- **Qargo API / Document API** — The API / Document API from Qargo — 2 operation(s) for api / document.
- **Qargo API / Order API** — The API / Order API from Qargo — 8 operation(s) for api / order.
- **Qargo API / Resource API** — The API / Resource API from Qargo — 8 operation(s) for api / resource.
- **Qargo API / Task API** — The API / Task API from Qargo — 3 operation(s) for api / task.
- **Qargo API / Trip API** — The API / Trip API from Qargo — 3 operation(s) for api / trip.
- **Qargo System API** — The System API from Qargo — 1 operation(s) for system.
- **Qargo Use case / Accounting API** — Required role: `API_ACCOUNTING`. See [Accounting](/docs/section/accounting) for more information.
- **Qargo Use case / Customer portal API** — Required api role: `CUSTOMER` This is the api equivalent of our customer portal functionality. Customers can use this api to create/update/cancel orders, view charges and receiv...
- **Qargo Use case / Document import API** — This section provides an overview of all available methods to import documents into Qargo. ![Document import paths overview](/docs/static/document_import_overview.svg) ### Docum...
- **Qargo Use case / E-invoicing API** — Required api role: not applicable Purpose: This interface allows an external party to send e-invoices in a structured format. A [webhook](/docs/use-case-e-invoicing/e-invoicing-...
- **Qargo Use case / Fleet dispatch API** — Required api role: not applicable (push/push) Purpose: This interface allows an external party to integrate with driver apps and on board computer systems. The fleet dispatch us...
- **Qargo Use case / Intermodal [partner] API** — Note: this is currently only a specification meant as a preview. Implementation is still pending.
- **Qargo Use case / Location booking API** — Required api role: not applicable (push/push) Purpose: This interface allows an external party to integrate with warehouse management systems and location booking platforms. The...
- **Qargo Use case / Master data sync API** — Required api role: `API_MASTER_DATA`, or `API_ACCOUNTING` for company sync only.
- **Qargo Use case / Order API** — Required api role: `API_ORDER` All endpoints related to order creation and status retrieval/subscription. ### Getting started See [this section](/docs/section/transport-order-cr...
- **Qargo Use case / Subcontractor dispatch API** — Required api role: not applicable (push/push) Purpose: This interface allows an external party to integrate with 3rd party transport management systems for subcontracting. The s...
- **Qargo Use case / Tracking API** — The Use case / Tracking API from Qargo — 1 operation(s) for use case / tracking.
- **Qargo Use case / Trip import API** — Required api role: `API_TRIP` Purpose: This interface allows an external system (e.g. a route optimisation tool) to send fully planned trips into Qargo. When a trip payload arri...
- **Qargo Use case / Visibility API** — The Use case / Visibility API from Qargo — 2 operation(s) for use case / visibility.
- **Qargo Webhooks / Inbound API** — Inbound webhooks use **Basic Authentication**, not OAuth2. See [Authentication](/docs/section/authentication) for details on how to authenticate webhook requests.
- **Qargo Webhooks / Outbound API** — Outbound webhooks are sent by Qargo to your system when certain events occur. Configure the receiving endpoint URL and credentials in the integration settings.

## MCP servers (1)

- **Qargo API documentation**

## Agentic access (1)

- **Qargo Agentic Access** — 114 operations · 64 acting · 7 human-in-the-loop

## Security (2)

- **Qargo Authentication** — oauth2/http · 2 schemes
- **Qargo Domain Security** — TLSv1.3 · DNSSEC · DMARC

## Tags

Company, Transport Management, Logistics, Supply Chain, Freight, TMS, Accounting, Webhook

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/qargo/). Scores are computed from the provider's own public artifacts under a published rubric.