The API Report CardAPI Index
Descartes

Descartes API

Fleet / Trucking / Logistics · descartes.com

REST APIs exist but are scattered across the acquisition portfolio: a central API portal, MacroPoint tracking APIs, and separate surfaces for Sellercloud, Aljex, and CustomsInfo. Access is per product, usually requiring an active license before docs and credentials are issued.

Last verified: July 2026Logistics & Supply Chain
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODReal REST APIs exist: a central Descartes API portal plus documented MacroPoint visibility APIs with webhooks.
AccessFAILRegistration and terms are per product, and many APIs require an active license before credentials are issued.
CoveragePOORCoverage is product-specific rather than uniform; each acquired line (Sellercloud, Aljex, pixi) has its own surface.
AuthFAILNo unified auth: credentials are issued per product, often only after license and account-management engagement.
Docs & DXFAILDocs, sandboxes, and rate limits are not uniformly public; many specs arrive only after you hold a license.
StabilityMIXEDLegacy EDI rails (X12, EDIFACT, AS2) are long-lived, but API lineages vary by acquisition across XML, SOAP, and REST.
Supergood: Descartes has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Descartes scores F on the API Report Card. REST APIs exist but are scattered across the acquisition portfolio: a central API portal, MacroPoint tracking APIs, and separate surfaces for Sellercloud, Aljex, and CustomsInfo. Access is per product, usually requiring an active license before docs and credentials are issued.

Tried to integrate with Descartes?