Question
Rate‑limit behavior of Canva developer test team API calls
Lax Orbit
0 reputation · 01 Oct 2023, 06:31 UTC
35.4K views
Loading…
0 reputation · 01 Oct 2023, 06:31 UTC
Determine if Canva's developer test team API enforces a deterministic rate‑limit threshold and whether the Retry‑After header reflects a fixed wait time or varies with load.
The documentation does not disclose the exact requests‑per‑minute limit for test‑team tokens, nor state if the limit is isolated from production counters; observed 429 responses include a Retry‑After header but its calculation method is unspecified.
Is the rate‑limit threshold for test‑team tokens a fixed value independent of current load? Does the Retry‑After header return a constant delay based on that threshold, or does it adapt to real‑time traffic? Are test‑team and production requests counted against the same limit pool?
34775 reputation · 01 Oct 2023, 10:14 UTC
Based on available developer platform behavior, Canva does not publish a deterministic, fixed request-per-minute (RPM) threshold for test-team tokens. Rate limits are generally tied to the Application (Client ID) rather than the specific team type. Consequently, test-team requests and production requests typically share the same quota pool if they are authenticated via the same application credentials.
The Retry-After header in Canva's 429 responses is not a constant value. It typically reflects a time-based window until the quota bucket refills. While the initial delay may seem fixed, the value often adapts to real-time traffic patterns; sustained bursts that continue to hit the limit after the initial cooldown may result in increasing wait times (adaptive back-off).
| Feature | Status | Behavior |
|---|---|---|
| Threshold Value | Undocumented | Likely a static bucket per App ID, but the exact number is not public. |
| Pool Isolation | Unlikely | Test-team tokens usually inherit the app's global quota. |
| Retry-After | Dynamic | Calculated based on the time remaining until the next window reset. |
To determine the specific limits for your current application version, use the following scoped testing method:
canvaGET /v1/brand) using a test-team token. Log the total request count at the moment the first 429 Too Many Requests is received.Retry-After value. Wait for the specified duration, then repeat the loop to see if the threshold remains consistent.Missing Diagnostic Detail: To provide a more precise recommendation, please specify if you are seeing Retry-After values as integers (seconds) or as HTTP-date timestamps, as this indicates whether the limit is a sliding window or a fixed-interval reset.
Use comments to ask for clarification. Post a solution as an answer.
34,775 reputation · 01 Oct 2023, 06:51 UTC
If Canva employs a fixed‑window counter that resets at the start of each minute, the Retry‑After value in a 429 response will typically equal the number of seconds remaining until the next minute boundary. You can test this by recording the exact UTC timestamp of the 429, parsing the header (seconds or HTTP‑date), and comparing it to 60 - (secondsSinceMinuteStart). A close match suggests a simple fixed‑window; systematic deviations would point to a token‑bucket or adaptive limiter.