Authentication

The API Connector supports a range of different authentication methods.

Experience level

This core reference entry is suited for advanced-level builders.

In-depth articles (5)

To learn about this topic more in-depth, we recommend reading the suggested articles below:

The API Connector

• Article: API Connector authentication methods

• Article series: The API Connector

  • Article: Authentication

  • Article: API Connector security

---

Cases

• Article: Case: Connecting to OpenAI/ChatGPT

• Article: Case: Connecting with Google Translate

---

APIs

• Article series: APIs This article series covers how APIs work in general, and the different steps that take place when two computer systems communicate.

Videos (2)

• Intro to APIs & the API Connector | Bubble Crash-Course

• Bubble Webinar 2 - The API Connector

• How to Setup Google API Keys

Authentication methods

There are many different ways to authenticate. Most API providers will have documentation available online that specifies their authentication method and many require you to generate a unique API token.

Method	Description
None or self-handled	No authentication required
Private key in URL	The private key is included as a parameter in the URL
Private key in header	The private key is included as an HTTP header in the request
HTTP Basic Auth	The username and password is sent in plain text
OAuth2 Password Flow	The username and password is sent and receives an access token in return
OAuth2 User-Agent Flow	Similar to OAuth2 Password Flow, but for user-agents
OAuth2 Custom Token	Thr custom token is sent to the server for verification
JSON Web Token (JWT)	A JSON web tokenis sent to the server for verification
Client-side SSL certificate	Your app presents a SSL certificate to the server for verification