Canva Rate Limits
Canva publishes a numeric per-operation rate limit on every Connect REST API reference page, expressed as requests per minute. For public or private apps (OAuth authorization code flow) the limit is counted "for each user of your app"; since 2026-11-06 service apps (OAuth client credentials flow) get a separate per-app limit, shown in a second table row. The design export job additionally carries app, document and user throttles over 5-minute and 24-hour windows. Exhaustion returns HTTP 429 with code `too_many_requests`. No rate-limit response headers (X-RateLimit-*, RateLimit-*, Retry-After) are documented. This replaces the 2026-08-13 file, which recorded limit_count 0 because it read only the guide pages and not the per-operation reference.
Canva Rate Limits is the rate-limit profile for Canva on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-11-11.
It captures 88 rate-limit definitions, including getDesignAnalyticsLinks (public-or-private-app) — 100 requests per minute for each user of your app; getDesignAnalyticsPageViews (public-or-private-app) — 100 requests per minute for each user of your app; getDesignAnalyticsViewers (public-or-private-app) — 100 requests per minute for each user of your app.
Limit state is signalled in the published, x_ratelimit, ratelimit_draft_headers, and retry_after response headers, and an exhausted limit returns HTTP 429.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled, error_code, example_body, and example_source.
Tagged areas include Apps, Automation, Design, Templates, and Rate Limiting.
publishedx_ratelimitratelimit_draft_headersretry_after
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.