Stop Using the Old Bubble API Plugin: Use the New Editor-Based API Connector

Published: (February 4, 2026 at 05:22 AM EST)
2 min read
Source: Dev.to

Source: Dev.to

Overview

Bubble is moving away from the old plugin‑based API Connector toward a new editor‑based version. If you rely on APIs in Bubble—especially for AI, payments, or third‑party services—this isn’t just a UI refresh; it changes how API configuration fits into the overall Bubble building experience.

What Changed

New Location in the Editor

The API Connector is now part of the Bubble editor itself, making API setup feel like a native step rather than an add‑on.

Key Improvements

  • Cleaner, more structured interface for endpoints, headers, and parameters
  • Better visibility into how APIs fit into workflows
  • Less context switching when building or debugging
  • A setup that scales better as your app grows

The new design feels aimed at serious apps, not just quick integrations.

What Stayed the Same

  • Endpoints are still defined with URLs, headers, and parameters
  • Authentication works largely the same way
  • Calls still need to be initialized
  • Responses remain reusable across workflows

If you’ve used the old API Connector before, you won’t feel lost.

Migration Process

There’s currently no automatic migration from the plugin‑based connector to the new editor‑based one. Migration is manual but manageable:

  1. Recreate existing endpoints in the new connector
  2. Copy authentication, headers, and parameters
  3. Initialize the calls
  4. Update workflows to point to the new API actions

For most apps, this is a careful copy‑and‑verify process rather than a full rewrite.

Demo: OpenAI Text‑to‑Speech

To illustrate the new connector, a demo calls the OpenAI Text‑to‑Speech endpoint directly from Bubble. Highlights include:

  • AI APIs fit naturally into the new connector
  • Configuration is clearer and easier to follow
  • The setup works cleanly with Bubble workflows

If you’re building AI‑powered features in Bubble, the new connector makes these integrations feel much more first‑class.

Conclusion

The old plugin still works, but it’s no longer the focus. The editor‑based API Connector is:

  • More integrated
  • Easier to maintain
  • Better aligned with modern Bubble apps

Switching early helps future‑proof your projects and reduces technical debt later. If you build serious applications in Bubble and rely on APIs, this update is worth your attention.

Back to Blog

Related posts

Read more »