Skip to main content
Rate limits decide how many requests per minute your systems can send to Zippendo, so your integrations, checkout and order imports keep running smoothly. Each kind of traffic has its own limit, and the limit grows with your plan. When a limit is reached, the API responds with HTTP 429, the error body { "code": "RATE_LIMITED", "error": "Too Many Requests", "message": "…" }, and a Retry-After header with the number of seconds until the window resets.

Limits by plan

All windows are 60 seconds. Every limit can be adjusted per organization: if your integration really needs more room than your plan gives, contact support. Notes:
  • API requests count every call made with an API token (zipp_) or an OAuth token against the organization’s budget. Using the Zippendo app does not count.
  • Checkout rate requests are counted per order channel, so one busy webshop never slows down another.
  • Order pushes to a custom channel’s ingest URL count only when they are correctly signed. ping deliveries are free. On a 429, retry after the delay given: sending the same order again is safe.
  • Order updates that Shopify and WooCommerce send to Zippendo have no plan limit.
  • MCP: tool calls your AI agent makes through the MCP server don’t count against the API budget. The connector URL has its own limit of 300 requests per minute per IP address.
  • On top of the plan limits, other requests from one IP address, such as the Zippendo app’s, share a separate ceiling, and sign-in and sign-up have stricter limits. These protect Zippendo against abuse. API-token requests from one server can use your plan’s full budget. If you get 429s while you are below your plan’s budget, contact support.

Handling 429s

Spread bulk work (for example importing thousands of orders) evenly across the minute instead of sending it in one burst: the window refills completely at each reset.