Article

API Connector security

Bubble · Bubble Docs Free Intermediate

When your app calls a paid service (OpenAI, a payment provider, an email tool), the key can end up visible in the browser if you set it up in the wrong place. This page explains where Bubble keeps those keys private (server side) versus where they leak (client side calls). Getting this right is how you avoid handing strangers your billing.

  • Mark third-party keys as server-side so they never render in the browser
  • Client-side API calls expose the key in the network tab
  • A leaked key can run up real charges on your account
Open on manual.bubble.io ↗

The question it answers

  1. How do I add proper user login and role-based access to a no-code app without leaving my data wide open?

Read with it

  1. This is the official, canonical explanation of the one feature that actually protects your data in Bubble. It makes the core... Bubble Docs Article Protecting data with privacy rules Bubble
  2. Your app has a second front door most builders forget: the Data API, a public URL that returns your tables as raw JSON. This... Bubble Docs Article Data API security Bubble
  3. Nothing makes the risk concrete like real numbers, and this audit of over 11,000 live Bubble apps found that most of them leak.... Bubble Forum Thread I Audited 11,026 Bubble Apps for Security, Here's What I Found ankur1
  4. If you learn better by watching someone click through the editor, this is the official video walkthrough of setting up privacy... Bubble Academy Course Bubble Academy: Security and Privacy Bubble
  5. This is the number one web security risk, and it is exactly your question: users reaching data they should not. OWASP is the... OWASP Article A01 Broken Access Control (OWASP Top 10) OWASP Foundation
  6. IDOR is the everyday version of the danger in one sentence: change the id in a URL or request from 1042 to 1043 and read... OWASP Article Insecure Direct Object Reference (IDOR) OWASP Foundation
eChai Partner Brands The partnership →