specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Karrio
providerId: karrio
generated: '2026-08-27'
method: searched
source: >-
  https://karrio.io/docs/api-reference, https://karrio.io/docs, https://karrio.io/platform
  and openapi/karrio-api-openapi.yml (Karrio API 2026.1.32).
created: '2026-05-04'
modified: '2026-08-27'
tags:
  - Shipping
  - Rate Limiting
  - Quotas
description: >-
  Karrio publishes NO rate limits. This is an honest zero, and for this provider it is
  also a defensible one: Karrio is deployed per instance — self-hosted or managed — so
  throughput is a property of the operator's own deployment, not of a shared multi-tenant
  gateway. What is missing regardless of deployment model is the runtime signal: the
  contract declares no 429 response and no rate-limit response header on any of its 95
  operations, so a client has no in-band way to learn it is being throttled by whatever
  sits in front of an instance.
limit_count: 0
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  published: false
responseCodes:
  throttled: null
  note: >-
    No 429 response is declared on any operation in the OpenAPI. The declared error codes
    are 400, 401, 404, 409, 424 and 500.
limits: []
evidence:
  - check: X-RateLimit-* / RateLimit-* / Retry-After headers in the OpenAPI
    result: zero occurrences across 496 KB of contract
  - check: 429 response declared on any of 95 operations
    result: none
  - check: rate limits or quotas on the pricing FAQ at https://karrio.io/platform
    result: 'HTTP 200; no limit stated for any of the three tiers'
  - check: https://karrio.io/pricing
    result: HTTP 404
downstream_note: >-
  The binding constraint on a Karrio integration is usually not Karrio but the carrier
  behind it. Carrier rate limits surface as HTTP 424 with the carrier's own message and
  carrier_name attribution — see errors/karrio-problem-types.yml. An agent should treat
  424 rather than 429 as the throttling signal on this API.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com