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
Qargo

Qargo Use case / Intermodal [partner] API

Note: this is currently only a specification meant as a preview.Implementation is still pending.

Documentation Provider Profile APIs.io OpenAPI GitHub

Qargo Use case / Intermodal [partner] API is one of 22 APIs that Qargo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Use case / Intermodal [partner]. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 2 operations across 2 paths, and defines 113 schemas. It is described by OpenAPI 3.2.0, at version 1.2.0.

Requests are made against a single base URL, https://api.qargo.com.

2 operations 2 paths 113 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.0
Base URL
https://api.qargo.com
Authentication
OAuth 2.0, HTTP Basic
Resource Areas
1

Authentication & Security 2

Qargo Use case / Intermodal [partner] API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oAuth2ClientCredentials) using the clientCredentials flow. It accepts HTTP basic authentication (BasicAuthWebhookCredentials).

Paths & Operations 2

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

Use case / Intermodal [partner] 2

Note: this is currently only a specification meant as a preview. Implementation is still pending.

POST
/v1/webhook/intermodal-status
Intermodal Booking Status Update Webhook
intermodal-booking-status-webhook body → 200400401403422429500503
POST
https://
Intermodal Booking Payload
Intermodal_booking_payloadhttps____intermodal_booking_receiving_payload__post body → 200400401403422429500503

Schemas 113

The contract defines 113 schemas that model the data the API accepts and returns. The most detailed are OrderOutput-Input (29 properties), GoodOutput-Input (28 properties), CompanyOutput-Input (21 properties), Booking (20 properties). Each schema is shown below with its type and property counts.

PackagingSize
object
8 properties
ADRPackagingType
string
DachserExtraFields
object
1 property
Container
object
13 properties
IntermodalBookingUpdate
object
9 properties
PalletlineExtraFields
object
1 property
StopDepotOutput
object
8 properties
TaxTypeEnum
string
ShippingLocation
object
16 properties
HTTPValidationError
object
1 property
FieldMatchInput
object
1 property
ExtraField
object
3 properties
Customs
object
2 properties
PackagedItemsImportExportExtraFields
object
7 properties
ADRPhysicalState
string
ADRType
string
IntermodalBookingStatusPayload
object
1 property 1 required
Position
object
2 properties 2 required
Signature
object
4 properties 1 required
ConsignmentOutput-Input
object
17 properties 3 required
PalletforceExtraFields
object
5 properties
ServiceLevel
object
3 properties
Department
object
2 properties
AdditionalGoodsInformation
object
3 properties
ErrorStatus
object
2 properties 1 required
CompanyReferenceNumbers
object
5 properties
DriverMode
string
ValidationErrorDetail
object
4 properties 1 required
IntermodalExecutionStatus
object
4 properties 3 required
PaymentTermCode
string
BookingDimensions
object
9 properties
BookingStatus
string
ValidationError
object
3 properties 3 required
BarcodeOutput
object
2 properties
HandlingUnitOutput-Input
object
2 properties 1 required
ConsignmentCustomsImportInfo
object
9 properties
IntermodalBookingPayload
object
3 properties 3 required
ContainerType
object
4 properties
ImportDeclarationTypeEnum
string
TransporeonOrderExtraFields
object
2 properties
ShippingCompany
object
2 properties
PackagingType
object
5 properties
PackagedItemCommercialInvoiceExtraField
object
1 property
CompanyOutput-Input
object
21 properties 3 required
ConsignmentImportExportExtraFieldsOutput-Input
object
4 properties
ShippingRoute
object
5 properties 2 required
TransporeonConsignmentExtraFields
object
1 property
ValidationErrorResponse
object
2 properties 2 required
Trailer
object
17 properties
Booking
object
20 properties 6 required
OrderOutput-Input
object
29 properties 3 required
GoodOutput-Input
object
28 properties 1 required
BankAccount
object
2 properties
BookingMatchTarget
object
1 property
Incoterm
string
Plugging
object
3 properties
ErrorType
string
KuehneNagelExtraFields
object
2 properties
ConsignmentCustomsTransitInfoOutput
object
9 properties 2 required
PackagedItemOutput-Input
object
14 properties 1 required
BarcodeSource
string
ContainerScenario
string
Incident
object
4 properties
Gateway
object
1 property 1 required
ContactType
string
LocationWithTerminalOutput-Input
object
15 properties
StopOutput-Input
object
19 properties 2 required
IntermodalExecutionStatusEnum
string
CentralTransportNetworkConsignmentExtraFields
object
3 properties
TransportType
object
2 properties 1 required
AdditionalExportBorderProcessEnum
string
ExportDeclarationTypeEnum
string
CustomsMetadata
object
1 property
IntermodalBookingsPushPayload
object
1 property 1 required
BookingVehicleType
string
PalletforceConsignmentExtraFields
object
1 property
StopExtra
object
3 properties
VehicleCategory
object
3 properties
Entity
object
2 properties
AdditionalTransitBorderProcessEnum
string
TimeWindow
object
7 properties
CompanyContactOutput
object
6 properties
LocationOutput
object
13 properties
OrderPricingOutput
object
5 properties
Vehicle
object
17 properties
AmazonExtraFields
object
8 properties
ConsignmentCustomsExportInfo
object
8 properties
ResourceTypeEnum
string
TemperatureRequirements
object
2 properties
BookingOperation
string
HSCode
object
2 properties
TransitDeclarationTypeEnum
string
BookingExecutionData
object
2 properties
ConsignmentTransportNetwork
object
3 properties
TransitOffice
object
1 property
ImportExportExtraFields
object
3 properties
IntermodalBookingReferences
object
2 properties
ConsignmentBuyerSellerOutput-Input
object
2 properties
PalletlineConsignmentExtraFields
object
1 property
ConsignmentCommercialInvoiceExtraField
object
3 properties
BookingMatch
object
2 properties
CustomerStatus
string
BuyerSellerCompanyOutput-Input
object
10 properties 2 required
ShippingStop
object
3 properties 1 required
AdditionalImportBorderProcessEnum
string
IntermodalStatuses
object
3 properties
BasePaymentTerm
object
1 property 1 required
TerminalMetadata
object
5 properties
IntermodalBookingPushPayload
object
3 properties 3 required
Product
object
4 properties
SignatureType
string
ADR-Input
object
14 properties
ContainerExtraFields
object
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qargo-use-case-intermodal-partner-api-openapi.yml Raw ↑

Other APIs Qargo publishes across the network.

Qargo Subcontractor API
AE Profile APIs.io
Qargo Customer API
AE Profile APIs.io
Qargo API / Accounting API
AE Profile APIs.io
Qargo API / Authentication API
AE Profile APIs.io
Qargo API / Company API
AE Profile APIs.io
Qargo API / Document API
AE Profile APIs.io
Qargo API / Order API
AE Profile APIs.io
Qargo API / Resource API
AE Profile APIs.io
Qargo API / Task API
AE Profile APIs.io
Qargo API / Trip API
AE Profile APIs.io
Qargo System API
AE Profile APIs.io
Qargo Use case / Accounting API
AE Profile APIs.io
#Use case / Intermodal [partner]
← Back to Q APIs
API Details
ID
qargo:qargo-use-case-intermodal-partner-api
Base URL
https://api.qargo.com
Docs
https://api-docs.qargo.com/docs
Provider
Qargo
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=qargo-use-case-intermodal-partner-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/qargo-use-case-intermodal-partner-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 Qargo Use case / Intermodal [partner] 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.