Canva Connect API vs the Sume API: what each is for
Canva Connect syncs designs, assets and comments, with some APIs in preview. The Sume API generates video, images and audio. Different jobs.

The Canva Connect APIs let your app work with a person's Canva designs, assets and comments, while the Sume API generates new video, images and audio from a prompt. If you need to read or export a design someone made in Canva, use Connect. If you need a clip to put into a design, generate it with Sume and bring it in.
Canva's own overview, read 2026-10-10 at canva.dev, says Connect is for creating and syncing assets, designs and comments, and warns that some APIs are in preview and not suited to production. Its export reference, read the same day, is at Create design export job.
Different jobs
A Connect integration acts on behalf of a Canva user. It works on things that already exist in their account, and the export call turns a design into a file. A Sume request starts from nothing: you send a prompt or a reference, and a model produces media. There is no equivalent in the Sume docs of a design document with pages and editable layers, so Sume cannot take the place of the design editor.
The shapes do rhyme. A Canva export is an asynchronous job whose status moves through in_progress, success and failed, and its download URLs expire after 24 hours. A Sume generation returns a job envelope you poll through GET /v1/jobs/:id/status until it is completed, failed or canceled, or you ask for a webhook.
| Question | Canva Connect | Sume API |
|---|---|---|
| Starting point | An existing design, asset or comment | A prompt, image or reference |
| Typical output | A file export: JPG, PNG, GIF, PPTX, MP4, PDF, CSV or HTML | A generated MP4, image or audio file |
| Job states | in_progress, success, failed | queued, processing, completed, failed, canceled |
| Download link life | Expires in 24 hours (export) | Not documented as a fixed time; fetch results promptly |
| Maturity note | Some APIs are preview, not for production | Documented as the public API |
A split that works
Teams that want both usually put generation first and layout second. Sume makes the clip, image or voice-over; a person or a Canva-side integration places it in a design; Connect exports the finished piece. Sume's docs do not describe a Canva integration, so the hand-off is yours to build, for instance by downloading the generated file and uploading it as a Canva asset through Canva's own documented routes.
Because Canva marks some Connect APIs as preview, check each endpoint's status in Canva's reference before you depend on it. The same discipline applies to Sume: read GET /v1/catalog and the model listing at runtime, not a copy from a blog post.
When Canva is the right answer
If the thing you need is a branded layout, a template with locked fonts, or a shared review of a design, that is Canva's job and Sume is not trying to do it. If the thing you need is footage that does not exist yet, Canva's export call will not produce it. Pick on that question first and the API choice follows.
Sources
Related posts
More in Comparisons
- CapCut lists Seedance 2.5 and Gemini Omni. Does Sume's API carry them?
CapCut's tools page names several video and image models. Sume's API documents Seedance 2.5 and Gemini Omni Flash 1.1; the rest are not in its docs.
- ChatGPT Image 2 vs 2.5 on Sume: $0.26375 vs $0.065875 and what differs
On Sume, GPT Image 2.5 high quality at 1024 costs $0.065875, a quarter of GPT Image 2 at $0.26375, and adds mask_url, background and 16 references.
- Creatomate RenderScript vs a Sume Timeline document: field map
Creatomate's RenderScript is a general scene JSON; Sume's Timeline 1.0 is one audio spine plus video slots. Field-by-field map and what Sume cannot express.
- Creatomate template modifications vs a Sume Format run input
Creatomate fills a fixed template through modifications; a Sume Format run takes free-form input and generates new media. Request shapes and when each fits.
Written by Sume