Apideck · Rate Limits

Apideck Rate Limits

Apideck does not publish a single global rate-limit number for its Unify API. Effective limits are determined by (1) Apideck's own per-application throttling and (2) the downstream connector's native rate limits (Salesforce, QuickBooks, Xero, HubSpot, etc.) which Apideck proxies and surfaces on 429. Apideck recommends honoring upstream Retry-After headers and using exponential backoff. Plan tier governs Active Consumer count and category access rather than a documented per-second cap.

Apideck Rate Limits is the machine-readable rate-limit profile for Apideck on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring varies.

Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Rate Limiting, Unified API, and Integrations.

2 Limits Exhausted: HTTP 429 retryAfter
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingUnified APIIntegrations

Limits

Apideck platform throttling application
varies
see provider documentation
Apideck does not publish a fixed per-second number; throttling is applied at the application and consumer level to protect shared infrastructure.
Connector (downstream) rate limits connector
varies
governed by downstream connector
When an upstream SaaS (Salesforce, QuickBooks, Xero, HubSpot, etc.) throttles, Apideck propagates a 429 with the upstream Retry-After.

Policies

Backoff Strategy
Implement exponential backoff with jitter; honor Retry-After when returned by Apideck or the underlying connector.
Connector Awareness
Effective throughput depends on the downstream system's native limits. High-volume use cases should partition workload across consumer connections and respect per-connector quotas.
Fair Use
Sustained traffic that materially impacts shared infrastructure may be throttled regardless of plan tier; engage Apideck support to align on burst patterns.
Webhook Replay
Use webhooks plus subscribe/poll patterns rather than tight read loops to reduce request volume against rate-limited connectors.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/apideck-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.