Skip to content

API and SDK endpoints

Look up the correct dashboard URL, REST API endpoint, and SDK endpoint for your Braze instance. You need these URLs to log in, make API calls, and integrate the SDK.

Braze manages a number of different instances for our dashboard, SDK, and REST endpoints, which we call “clusters.” Your Braze onboarding manager will let you know which cluster you’re on. To learn more about the Braze SDK, check out the Braze 101 Braze Learning course.

Logging in at dashboard.braze.com automatically sends you to the correct cluster address.

Instance URL REST Endpoint SDK Endpoint
US-01 https://dashboard-01.braze.com https://rest.iad-01.braze.com sdk.iad-01.braze.com
US-02 https://dashboard-02.braze.com https://rest.iad-02.braze.com sdk.iad-02.braze.com
US-03 https://dashboard-03.braze.com https://rest.iad-03.braze.com sdk.iad-03.braze.com
US-04 https://dashboard-04.braze.com https://rest.iad-04.braze.com sdk.iad-04.braze.com
US-05 https://dashboard-05.braze.com https://rest.iad-05.braze.com sdk.iad-05.braze.com
US-06 https://dashboard-06.braze.com https://rest.iad-06.braze.com sdk.iad-06.braze.com
US-07 https://dashboard-07.braze.com https://rest.iad-07.braze.com sdk.iad-07.braze.com
US-08 https://dashboard-08.braze.com https://rest.iad-08.braze.com sdk.iad-08.braze.com
US-10 https://dashboard.us-10.braze.com https://rest.us-10.braze.com sdk.us-10.braze.com
EU-01 https://dashboard-01.braze.eu https://rest.fra-01.braze.eu sdk.fra-01.braze.eu
EU-02 https://dashboard-02.braze.eu https://rest.fra-02.braze.eu sdk.fra-02.braze.eu
AU-01 https://dashboard.au-01.braze.com https://rest.au-01.braze.com sdk.au-01.braze.com
ID-01 https://dashboard.id-01.braze.com https://rest.id-01.braze.com sdk.id-01.braze.com
JP-01 https://dashboard.jp-01.braze.com https://rest.jp-01.braze.com sdk.jp-01.braze.com
KR-01 https://dashboard.kr-01.braze.com https://rest.kr-01.braze.com sdk.kr-01.braze.com

For details about accessing the API, see our API overview article.

Custom URLs

Instead of the standard SDK endpoint for your cluster, you can configure the Braze SDK to send its network requests to a custom URL, such as a proxy or a custom domain. The following SDKs support custom URLs:

Configuring a custom URL

Set your custom URL where you set your SDK endpoint when you initialize the SDK. For the full integration steps, see Integrate the Braze SDK.

Pass your custom URL as the endpoint when you create your Braze.Configuration object. For the full initialization steps, see Step 3: Update your app delegate.

let configuration = Braze.Configuration(
  apiKey: "YOUR_APP_IDENTIFIER_API_KEY",
  endpoint: "YOUR_CUSTOM_URL"
)
let braze = Braze(configuration: configuration)
AppDelegate.braze = braze
BRZConfiguration *configuration = [[BRZConfiguration alloc] initWithApiKey:@"YOUR_APP_IDENTIFIER_API_KEY"
                                                                  endpoint:@"YOUR_CUSTOM_URL"];
Braze *braze = [[Braze alloc] initWithConfiguration:configuration];
AppDelegate.braze = braze;

Replace the following:

  • YOUR_APP_IDENTIFIER_API_KEY: The app identifier API key from the App Settings page in the Braze dashboard.
  • YOUR_CUSTOM_URL: Your proxy or custom domain URL.

In Swift SDK version 11.8.0 and later, your custom URL can include a base path (for example, example.com/mockServer) and can use the http scheme. For more information, see the Swift SDK changelog.

You can set your custom URL in your braze.xml file or in code. For the full integration steps, see Step 2: Configure your braze.xml.

Option 1: In your braze.xml file

Set the com_braze_custom_endpoint string to your custom URL.

<?xml version="1.0" encoding="utf-8"?>
<resources>
  <string translatable="false" name="com_braze_api_key">YOUR_APP_IDENTIFIER_API_KEY</string>
  <string translatable="false" name="com_braze_custom_endpoint">YOUR_CUSTOM_URL</string>
</resources>

Option 2: In code

Call setCustomEndpoint() on your BrazeConfig.Builder, and then pass the result to Braze.configure().

BrazeConfig brazeConfig = new BrazeConfig.Builder()
  .setApiKey("YOUR_APP_IDENTIFIER_API_KEY")
  .setCustomEndpoint("YOUR_CUSTOM_URL")
  .build();
Braze.configure(this, brazeConfig);
val brazeConfig = BrazeConfig.Builder()
  .setApiKey("YOUR_APP_IDENTIFIER_API_KEY")
  .setCustomEndpoint("YOUR_CUSTOM_URL")
  .build()
Braze.configure(this, brazeConfig)

Replace the following:

  • YOUR_APP_IDENTIFIER_API_KEY: The app identifier API key from the App Settings page in the Braze dashboard.
  • YOUR_CUSTOM_URL: Your proxy or custom domain URL.

In Android SDK version 9.0.1 and later, your custom URL can include a scheme and a base path.

If you set a custom IBrazeEndpointProvider on the Braze instance after you configure the SDK, it overrides the endpoint you set in BrazeConfig. For more information, see setEndpointProvider().

Testing your proxy configuration

Test that your proxy works as you expect before you release your app to production. To confirm that the SDK sends requests to your custom URL, use verbose logging:

  1. Enable verbose logging in your development build before you initialize the SDK. For the code for each SDK, see Verbose logging.
  2. Run your app on a test device or simulator. The SDK sends a request when a session starts.
  3. In your logs, find the request entries and confirm the request URL matches your custom URL.
  4. Confirm your proxy receives the requests from the SDK.

If you don’t see any requests to your custom URL on Android, verify your API key and endpoint configuration. For examples of what request entries look like in the logs, see Reading verbose logs.

New Stuff!