Feature activation

👍

To enable this feature on your app, please contact us.

This guide explains how to use the Bridge API to programmatically create multiple production applications in a single request. This feature is ideal for partners who need to scale their integration quickly and manage multiple client environments.

Prerequisites

Before you can use the Bulk Application Creation endpoint, ensure the following requirements are met:

• 2FA Activation: For security purposes, Two-Factor Authentication (2FA) must be activated on your Bridge Dashboard account.
• Primary Application Link: The email_customer provided in your requests must be associated with your primary Bridge application.

Endpoint Rules & Constraints

To ensure security and system stability, the following rules apply to all bulk creation requests:

• Uniqueness: Every app_name must be unique across the Bridge ecosystem.
• Batch Limits: You can create between 1 and 50 applications per API call.
• Rate Limiting: This endpoint is limited to a maximum of 1 request per minute.
• IP Whitelisting: We currently only support individual IP addresses using /32 notation (e.g., 192.168.1.1/32).
• Atomic Transactions: If a single error occurs within a batch (e.g., a duplicate name or invalid IP), no applications will be created. The request is "all or nothing."

The flow

API Reference

Request Example

curl --request POST \
     --url https://api.bridgeapi.io/v3/applications \
     --header 'Bridge-Version: BRIDGE-VERSION' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'Client-Id: MY_CLIENT_ID' \
     --header 'Client-Secret: MY_CLIENT_SECRET' \
     --data '
{
  "dashboard_user_email": "[email protected]",
  "applications": [
    {
      "name": "Application 1"
    },
    {
      "name": "Application 2"
    }
  ]
}
'

Success (204 No Content) Upon a successful request, the API will return a 204 No Content status code.

Credential Delivery

For security reasons, the API credentials (app_client_id and app_client_secret) are not returned in the JSON response. Instead, they are automatically sent via email to the email_customer address configured in the request.

❗️

Security Warning: Once you receive the app_client_id and app_client_secret, ensure you store them in a secure environment (such as a Secret Manager or encrypted vault). Do not share these credentials or commit them to version control.