Qargo
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.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Qargo the way a machine reads it — 52 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Qargo scores 47.1/100 (developing), with a separate agent-readiness read of 36/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Qargo's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/qargo/"
title="Qargo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qargo.svg"
alt="Qargo Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/qargo/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/qargo/"
title="Qargo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qargo/card.svg"
alt="Qargo Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Qargo
Each block below is one kind of artifact we hold for Qargo. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
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 / Document import API
This section provides an overview of all available methods to import documents into Qargo.  ### 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 / 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.
Scroll within the panel for all 22 ·
Open Collections 25
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONQargo TMS API / Accounting API
OPEN COLLECTIONQargo TMS API / Accounting API / Authentication API
OPEN COLLECTIONQargo TMS API / Accounting API / Company API
OPEN COLLECTIONQargo TMS API / Accounting API / Document API
OPEN COLLECTIONQargo TMS API / Accounting API / Order API
OPEN COLLECTIONQargo TMS API / Accounting API / Resource API
OPEN COLLECTIONQargo TMS API / Accounting API / Task API
OPEN COLLECTIONQargo TMS API / Accounting API / Trip API
OPEN COLLECTIONQargo TMS API / Accounting System API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Accounting API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Customer portal API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Document import API
OPEN COLLECTIONQargo TMS API / Accounting Use case / E-invoicing API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Fleet dispatch API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Location booking API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Master data sync API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Order API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Tracking API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Trip import API
OPEN COLLECTIONQargo TMS API / Accounting Use case / Visibility API
OPEN COLLECTIONQargo TMS API / Accounting Webhooks / Inbound API
OPEN COLLECTIONQargo TMS API / Accounting Webhooks / Outbound API
OPEN COLLECTIONScroll within the panel for all 25 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Qargo API documentation
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Qargo Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Qargo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/qargo · machine-readable index on apis.io
This is an independent, third-party profile of Qargo, 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.