Skip to main content
Call the Connect Backend API from your server. Use a Backend API key issued for your Connect project and keep it in server-side secret configuration.

​
Bearer authentication

Versioned Backend API keys can be sent directly as bearer tokens:
The key must grant the operation’s permission and satisfy its expiry and IP restrictions. Observe API keys and Connect tokens are not Backend API credentials.

​
HTTP Basic authentication

HTTP Basic authentication is also supported. The username is the project ID and the password is the API secret:
curl --user constructs the base64-encoded projectID:apiSecret header. Do not send the API secret alone as the Basic credential.

​
Permissions

The permission is also listed on each endpoint. A key with verification permission does not need user deletion permission.

​
Client SDKs

Client applications receive action-specific Connect tokens from your backend. The frontend protocol also uses a process token managed by the SDK. Neither requires exposing Backend API credentials in the client.