Have feedback on Canva's Design Editing API beta? Chat directly with our team!

Announcements
,
1

Hey Canva Developers,

Thanks to everyone who’s tried out the beta version of our Design Editing API! We’re excited to hear directly from you about your experience. What worked, what didn’t, and how we can improve.

We’re inviting community members to participate in a brief 30-45 minute feedback session with Voislav from the Canva team. Your insights are extremely valuable and will shape the future of the API.

If you’re interested in sharing your thoughts just reply below, and we’ll set up a convenient time to chat.

We can’t wait to hear from you!

1 Like
2

Hey Voislav, excited to see you working on this. Our app could really use this API. Here’s my problems with it:

  • I can’t edit multiple pages

  • I don’t get a unique ID for the element when I’m iterating

  • The canva/intents requires me to downgrade to Nove 18 which is not even maintained anymore

  • The docs are awkwardly put together on a bunch of different pages. The use cases that are shown in code samples is rarely how an app dev would use this API. The docs show iterating through elements to make changes but typically you would have references to all of all the elements in your state, then based on some event, you would make changes to a a specific element with the selected ID. This use case isn’t really shown in the code samples.

Just sent you an email on this, would love to show you the problems I’m running if it could help.

Cheers,
Sukh

2 Likes
3

Heya @sssaini1995 , for this one

The canva/intents requires me to downgrade to Nove 18 which is not even maintained anymore

could you check the engines field in your app’s package.json file? It should look something like this:

  "engines": {
    "node": "^18 || ^20.10.0",
    "npm": "^9 || ^10"
  },
4

Thanks for reaching out Sukh!

Replied on email :slight_smile:

1 Like
5

It does yeah. Looks like it came with the sample project from Canva. Is this a hard requirement or should I be able to remove it?

6

the engines field doesn’t actually impose any restrictions on the versions of node or npm you’re able to use, but it will display a warning if you’re using anything other than those version ranges listed. You can ignore this warning.
If you’re seeing an actual error, then you may have configured engines-strict in your local NPM install, in which case you can either disable engines-strict or remove the engines section from your app’s package.json

1 Like