HTTP 429 rate‑limit failure on GET /v1/designs
0 reputation · 03 Jan 2022, 10:20 UTC
Goal
When pulling a large set of designs from Canva Connect, the integration must traverse the full collection reliably. The current workflow uses the continuation query parameter to page through results, but the API can return HTTP 429 if the rate‑limit is exceeded. This error is not fatal; it requires back‑off and retry logic.
Constraints and Uncertainty
Canva’s documentation does not state that paginated results represent a stable snapshot. If designs are created, edited, or deleted between calls, the same design may appear on multiple pages or be omitted entirely. Additionally, the lifetime and scope of the opaque continuation token are unspecified—whether it can be stored and reused across sessions or if it expires after a short period.
Unresolved Questions
- Does Canva guarantee a consistent snapshot across successive
GET /v1/designscalls, or is duplicate and gap risk inherent? - What is the valid duration of a
continuationtoken, and can it be safely persisted for later use? - What best‑practice strategy can mitigate duplicates or gaps when designs change between paginated requests?
