Integrations are becoming part of Apps in the Developer Portal (Soon!)

Announcements
, ,
1

Hey developers :waving_hand:

We wanted to give you an early heads-up about a change coming to the Developer Portal. On 21st September, we’re bringing Apps and Integrations together in the Developer Portal. From then on, you’ll create new Integrations as Apps. Existing integrations will keep working. This post explains what that means and what (if anything) you need to do.

What’s changing

Today the Developer Portal has two separate things you can build: Apps (built with the Apps SDK, run inside Canva) and Integrations (built with the Connect API, run on your platform). They’ve had different creation flows, different settings, and different review processes.

We’re bringing them together under a single App. An App will be able to run inside Canva through Intents, integrate Canva with other platforms through REST APIs, or both. An App that only uses REST API is the equivalent of today’s Integrations, with a few things Integrations never had:

  • Versioning — publish new versions without a support ticket

  • Collaborators — invite and select collaborators to help configure and manage

  • Self-serve configuration — update your OAuth settings, scopes, and redirect URLs yourself

  • Apps Marketplace listing – publish a listing in the Apps Marketplace so users can discover your Canva integration

  • One place to manage everything you’ve built on Canva

What this means for you

If you have existing Integrations:

  • Your Integrations keep working. Nothing changes for your users or your OAuth clients.

  • From 21st September, you’ll no longer be able to create new Integrations from the Your Integrations tab. Instead, you’ll create an App and add REST API capabilities to it.

  • You’ll also no longer be able to submit an existing Integration for review. If you have a draft Integration you were planning to publish, we recommend submitting it before 21st September, or waiting and submitting it as an App.

  • Existing Integrations can still be updated by contacting support, as they can today.

  • We’ll provide a migration path to move your Integrations over to Apps after launch. You won’t need to rebuild anything, and we’ll share details here when it’s ready.

If you have existing Apps:

  • No action needed. You’ll be able to add REST API capabilities to your Apps when the change goes live, but you don’t have to.

If you’re just getting started:

  • Nothing to do right now. When the change lands, you’ll create an App and pick the capabilities you need.

What’s not changing

  • The Connect API itself: no endpoint, scope, or auth changes

  • The Apps SDK

  • Your existing OAuth clients, tokens, and user connections

Timeline

  • Now: We’re updating the Connect API and Apps SDK documentation to reflect the unified model.

  • 21st September: New Integration creation is turned off in the Developer Portal, and App creation with REST API capabilities goes live.

  • After launch: Migration path for existing Integrations. We’ll post here when it’s available.

We’ll update this thread as dates firm up.

Questions?

Drop them below. If you’ve got an Integration in flight and aren’t sure what to do, reply here and we’ll help you sort it out.

6 Likes