Canva REST APIs + MCP vs Creatomate

Canva REST APIs + MCP

OpenAPI 3.0 with 59 described operations, per-user rate limits and a 78-value error code enum. No server-to-server key, so unattended batch rendering has to run under one user's OAuth grant.

Creatomate

A hosted MCP server with eight tools, OAuth with PKCE and per-project connections sits beside a small REST API whose errors carry a hint and a documentation link, and dry_run validates a render at no cost. No status page, changelog, OpenAPI file or security contact was found, and the terms and privacy policy date from June 2022.

Canva REST APIs + MCP

1. Call the user capabilities endpoint before autofill, brand templates or resize, which need Pro or above
2. Poll export, upload and autofill jobs with exponential backoff and download results within 24 hours
3. Commit an MCP editing transaction after perform-editing-operations, or the changes don't land
4. Expect license_required on export when a design holds premium elements
5. Read page_number, not the deprecated index, from Get design pages

Creatomate

1. Send "dry_run": true to POST /v2/renders before a paid render. It returns valid, errors, warnings and the effective source
2. Read warnings on every render response. A modification keyed to an unknown element or property name is ignored without an error
3. Keep under 30 requests per 10 seconds across the whole account, and wait for Retry-After on a 429
4. Download each file when the webhook fires. Renders, their URLs and their status records are deleted after 30 days
5. Use render_scale 0.5 for draft videos, about a quarter of the credits, and remember MCP create_render spends credits without a confirmation step from the server