Descartes Systems Group · Rate Limits

Descartes Rate Limits

Descartes does not publish fixed numeric rate limits for its product APIs. Throughput and quotas are governed by each customer's contract and product subscription (MacroPoint tracked-load volume, CustomsInfo/Datamyne data entitlements, B2B connectivity agreements) rather than by a public per-minute request cap. Asynchronous MacroPoint updates are pushed to customer-hosted HTTP callback URLs, so notification volume follows shipment activity rather than a client-poll limit. Numeric limits below are not documented publicly and should be confirmed with Descartes.

Descartes Rate Limits is the machine-readable rate-limit profile for Descartes Systems Group on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and messages.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Logistics, Supply Chain, Freight Visibility, Customs Compliance, and Rate Limiting.

4 Limits Throttle: not published
LogisticsSupply ChainFreight VisibilityCustoms ComplianceRate LimitingQuotas

Limits

MacroPoint Visibility API Requests account
requests
not published
Governed by MacroPoint customer contract and tracked-load volume; no public request-rate cap documented.
MacroPoint Capacity Import/Export account
requests
not published
Import/Export API throughput follows the Capacity subscription; not publicly enumerated.
Trade Content / Trade Data API Calls account
requests
per contract
CustomsInfo and Datamyne API entitlements are set per subscription/contract.
B2B Connectivity Messaging account
messages
per contract
Global Logistics Network messaging volume governed by the connectivity agreement.

Policies

Contract-Governed Quotas
API throughput and quotas are defined by each customer's product subscription and contract rather than a public rate-limit policy.
Callback Delivery
MacroPoint delivers Location Updates, Order Status Change, Trip Event Updates, and Form Submits to customer-hosted HTTP callback URLs; the receiving endpoint must be able to absorb bursts tied to shipment activity.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After guidance provided by Descartes support on throttling.

Sources