# Braze Destination Config Reference


> Complete Rudder CLI reference for the Braze destination config keys, API and app identifier keys, cloud, device, and hybrid mode settings, and secrets.



[Braze](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/setup-guide/) is a customer engagement destination. RudderStack sends events to Braze's REST API from its servers, loads Braze's own SDKs in device mode, or combines the two in hybrid mode.

In a Braze destination spec:

- `type: braze`
- `definition_version: 1`

## Sample configuration

```yaml
version: rudder/v1
kind: destination
metadata:
  name: braze-prod
spec:
  id: braze-prod
  display_name: Braze Production
  type: braze
  definition_version: 1
  enabled: true
  config:
    data_center: US-03
    rest_api_key: "{{ .BRAZE_REST_API_KEY }}"
    use_platform_specific_api_keys: false
    app_key: "{{ .BRAZE_APP_KEY }}"

    enable_subscription_group_in_group_call: false
    enable_nested_array_operations: false
    send_purchase_event_with_extra_properties: false
    use_ecommerce_recommended_events: true
    support_dedup: true

    enable_braze_logging:
      web: false
    enable_push_notification:
      web: true
    allow_user_supplied_javascript:
      web: false
    track_anonymous_user:
      web: true

    connection_mode:
      web: hybrid
      ios_swift: device
      cloud: cloud
    consent_management:
      web:
        - provider: oneTrust
          consents:
            - marketing
```

The above example uses one app identifier key for every platform. Because some sources connect in `device` or `hybrid` mode and others in `cloud` or `hybrid`, it needs both `app_key` and `rest_api_key` — see [Key dependencies](#key-dependencies).

## Config keys

`config` accepts only the keys listed below. The [shared config key rules](https://www.rudderstack.com/docs/rudder-cli/destination-types/#config-key-rules) cover unknown keys, defaults, and immutability.

### Key dependencies

Which keys Braze needs depends on the modes your sources connect in. Rudder CLI enforces each requirement below.

| Key | Required when |
| :-----| :-----|
| `rest_api_key` | Any source connects in `cloud` or `hybrid` mode. Also checked per connection — see [Connect a source](#connect-a-source). |
| `app_key` | `use_platform_specific_api_keys` is `false` and any source connects in `device` or `hybrid` mode |
| `android_api_key` | `use_platform_specific_api_keys` is `true` and `android`, `android_kotlin`, `react_native`, or `flutter` connects in `device` or `hybrid` mode |
| `ios_api_key` | `use_platform_specific_api_keys` is `true` and `ios`, `ios_swift`, `react_native`, or `flutter` connects in `device` or `hybrid` mode |
| `web_api_key` | `use_platform_specific_api_keys` is `true` and `web` connects in `device` or `hybrid` mode |

**Warning:** Write `use_platform_specific_api_keys` out whenever a source connects in `device` or `hybrid` mode. When it's omitted, neither Rudder CLI nor the API asks for `app_key` or any platform key — so the spec validates and applies, and device mode has no app identifier key to load Braze with.

### Connection

<div class="rs-ckeys">
<div class="rs-ckey" id="data_center">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">data_center</p>Required</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  <a href="https://www.braze.com/docs/user_guide/data/data_centers/#list-of-data-centers" >Braze data center</a> of your account — visible in your Braze dashboard URL.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>One of <code>US-01</code> to <code>US-08</code>, <code>EU-01</code> to <code>EU-03</code>, or <code>AU-01</code>.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
<li>The dashboard defaults this field to <code>US-01</code>. Rudder CLI requires it explicitly.</li>
<li>A spec that omits this key fails validation.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/setup-guide/#supported-braze-data-centers" >Supported Braze data centers</a>.
</div>

</div>

<div class="rs-ckey" id="rest_api_key">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">rest_api_key</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Braze REST API key, used whenever RudderStack calls Braze from its servers.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when any source connects in <code>cloud</code> or <code>hybrid</code> mode. Leave it unset otherwise.</li>
<li>At most 100 characters, and must not contain line breaks.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  The key needs the <code>users.track</code> permission, among others. See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/setup-guide/#where-can-i-find-the-braze-rest-api-key" >Where can I find the Braze REST API Key?</a>.
</div>

</div>

</div>

### App identifier keys

Braze's SDKs need an app identifier key. Use `app_key` for every platform, or set `use_platform_specific_api_keys: true` and give each platform its own key for separate attribution in Braze.

<div class="rs-ckeys">
<div class="rs-ckey" id="use_platform_specific_api_keys">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">use_platform_specific_api_keys</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Use a separate app identifier key per platform instead of the single <code>app_key</code>. The dashboard marks this setting as beta and defaults it to <code>false</code>.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies when a source connects in <code>device</code> or <code>hybrid</code> mode.</li>
<li>Has no default in Rudder CLI — see <a href="#key-dependencies" >Key dependencies</a>.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="app_key">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">app_key</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Braze default app identifier key, used for every platform.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when <code>use_platform_specific_api_keys</code> is <code>false</code> and any source connects in <code>device</code> or <code>hybrid</code> mode.</li>
<li>At most 100 characters, and must not contain line breaks.</li>
<li>A <code>{{ path || fallback }}</code> template is accepted in place of a literal.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/setup-guide/#where-can-i-find-the-braze-default-app-identifier-key" >Where can I find the Braze Default App Identifier Key?</a>.
</div>

</div>

<div class="rs-ckey" id="android_api_key">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">android_api_key</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  App identifier key for Android. React Native and Flutter apps use it for their Android builds.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when <code>use_platform_specific_api_keys</code> is <code>true</code> and <code>android</code>, <code>android_kotlin</code>, <code>react_native</code>, or <code>flutter</code> connects in <code>device</code> or <code>hybrid</code> mode.</li>
<li>At most 100 characters, and must not contain line breaks. A template is accepted.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="ios_api_key">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">ios_api_key</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  App identifier key for iOS. React Native and Flutter apps use it for their iOS builds.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when <code>use_platform_specific_api_keys</code> is <code>true</code> and <code>ios</code>, <code>ios_swift</code>, <code>react_native</code>, or <code>flutter</code> connects in <code>device</code> or <code>hybrid</code> mode.</li>
<li>At most 100 characters, and must not contain line breaks. A template is accepted.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="web_api_key">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">web_api_key</p>RequiredSecret</div>
  <p class="rs-ckey__field">
    Type:
    <code>string</code>
  </p>
<p class="rs-ckey__field">
  Description:
  App identifier key for the web SDK.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Required when <code>use_platform_specific_api_keys</code> is <code>true</code> and <code>web</code> connects in <code>device</code> or <code>hybrid</code> mode.</li>
<li>At most 100 characters, and must not contain line breaks. A template is accepted.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  The dashboard describes falling back to <code>app_key</code> when a platform key is blank, but Rudder CLI and the API both require each platform key whose condition is met.
</div>

</div>

</div>

### Event settings

<div class="rs-ckeys">
<div class="rs-ckey" id="enable_subscription_group_in_group_call">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">enable_subscription_group_in_group_call</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Send the subscription group status in <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/cloud-mode/#group" ><code>group</code></a> events.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies to <code>cloud</code> mode only.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="enable_nested_array_operations">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">enable_nested_array_operations</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Use Braze&rsquo;s nested custom attributes to update custom attribute objects. The dashboard calls this <strong>Use Custom Attributes Operation</strong>.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies to <code>cloud</code> mode only.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/cloud-mode/#send-user-traits-as-nested-custom-attributes" >Send user traits as nested custom attributes</a>.
</div>

</div>

<div class="rs-ckey" id="send_purchase_event_with_extra_properties">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">send_purchase_event_with_extra_properties</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Include custom properties in purchase events.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies to <code>cloud</code> mode only.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="use_ecommerce_recommended_events">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">use_ecommerce_recommended_events</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>true</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Map RudderStack ecommerce <code>track</code> events such as <strong>Product Viewed</strong> and <strong>Order Completed</strong> to Braze&rsquo;s <code>ecommerce.*</code> recommended events. When <code>false</code>, they&rsquo;re sent as legacy custom and purchase events. The dashboard marks this setting as beta.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>Applies to both <code>cloud</code> and <code>device</code> mode.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/recommended-ecommerce-events/" >Braze Recommended Ecommerce Events</a>.
</div>

</div>

<div class="rs-ckey" id="support_dedup">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">support_dedup</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>boolean</code>
  </p><p class="rs-ckey__field">
    Default value:
    <code>false</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Deduplicate traits on <code>identify</code> and <code>track</code> calls, using Braze&rsquo;s <code>/users/export/ids</code> API to fetch existing attributes. If Braze&rsquo;s rate limit is hit, RudderStack sends all attributes without deduplicating.
</p>

<div class="rs-ckey__extra">
  See <a href="https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/trait-deduplication/" >Braze trait deduplication</a>.
</div>

</div>

</div>

### Web SDK settings

These keys configure Braze's web SDK, so they apply only when `connection_mode.web` is `device` or `hybrid`. Each is an object keyed by `web`, with a boolean value.

<div class="rs-ckeys">
<div class="rs-ckey" id="enable_braze_logging">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">enable_braze_logging</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Show Braze SDK logs in the browser console.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>web</code> — boolean.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="enable_push_notification">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">enable_push_notification</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Use Braze <a href="https://www.braze.com/docs/developer_guide/platform_integration_guides/web/push_notifications/integration" >web push notifications</a>. Requires a service worker on your site.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>web</code> — boolean.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="allow_user_supplied_javascript">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">allow_user_supplied_javascript</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Enable HTML in-app messages, which can run JavaScript you supply in Braze.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>web</code> — boolean.</li>
</ul>

</div>

</div>

<div class="rs-ckey" id="track_anonymous_user">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">track_anonymous_user</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Track activity from anonymous users and send it to Braze.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>web</code> — boolean.</li>
</ul>

</div>

</div>

</div>

### Event filtering

**Warning:** [Client-side event filtering](https://www.rudderstack.com/docs/sources/event-streams/sdks/event-filtering/) applies only to sources connected in `device` mode — the dashboard shows these controls only then, and the SDK is what applies the filter. Rudder CLI accepts the block in any mode, but it has no effect on cloud-mode events, or on the events hybrid mode sends through the API.

<div class="rs-ckeys">
<div class="rs-ckey" id="event_filtering">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">event_filtering</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Restricts which <code>track</code> events the SDK passes to Braze, by event name.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li><code>whitelist</code> — array of event names to allow; every other <code>track</code> event is dropped.</li>
<li><code>blacklist</code> — array of event names to drop; every other <code>track</code> event is allowed.</li>
<li>The two are mutually exclusive, and Rudder CLI enforces it — setting both fails validation.</li>
<li>Each name is at most 100 characters, or a <code>{{ path || fallback }}</code> template.</li>
</ul>

</div>

</div>

</div>

### Per-source keys

Both keys are objects keyed by the local source type — the tokens listed under [Source types](#source-types). A key naming a source type this destination doesn't support fails validation.

<div class="rs-ckeys">
<div class="rs-ckey" id="connection_mode">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">connection_mode</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Maps each source type you connect to the mode its events reach Braze in, using the modes in <a href="#source-types" >Source types</a>. It also decides which API and app identifier keys are required.
</p>

<div class="rs-ckey__notes">
  <p class="rs-ckey__field">Notes:</p>
  <ul>
<li>An entry is required for each source type you connect — see <a href="#connect-a-source" >Connect a source</a>.</li>
<li>A mode the source type doesn&rsquo;t support on this destination fails validation — for example <code>hybrid</code> for <code>react_native</code>.</li>
</ul>

</div>

<div class="rs-ckey__extra">
  <div class="rs-code">
  <div class="rs-code__head">yaml<button class="rs-code__copy" type="button">
      
      Copy
    </button>
  </div>
  <div class="highlight"><pre class="chroma"><code class="language-yaml" data-lang="yaml">connection_mode:
  web: hybrid
  ios_swift: device
  react_native: device
  cloud: cloud</code></pre></div>
</div>
</div>

</div>

<div class="rs-ckey" id="consent_management">
  <div class="rs-ckey__title">
    <p class="rs-ckey__name">consent_management</p></div>
  <p class="rs-ckey__field">
    Type:
    <code>object</code>
  </p>
<p class="rs-ckey__field">
  Description:
  Consent provider configuration per source type. The entry shape, accepted providers, and the rules on <code>resolution_strategy</code> and <code>consents</code> are shared across all destination types — see <a href="https://www.rudderstack.com/docs/rudder-cli/destination-types/#consent-management" >Consent management</a>.
</p>

</div>

</div>

## Source types

Braze accepts events from these source types in the mentioned connection modes:

| Source type | Connection mode |
| :-----| :-----|
| `android` | `cloud`, `device`, `hybrid` |
| `android_kotlin` | `cloud`, `device`, `hybrid` |
| `ios` | `cloud`, `device`, `hybrid` |
| `ios_swift` | `cloud`, `device`, `hybrid` |
| `web` | `cloud`, `device`, `hybrid` |
| `unity` | `cloud` |
| `cloud` | `cloud` |
| `react_native` | `cloud`, `device` |
| `flutter` | `cloud`, `device` |
| `cordova` | `cloud` |
| `warehouse` | `cloud` |

In `hybrid` mode, RudderStack sends every user-generated event — `identify`, `track`, `page`, `screen`, `group`, and `alias` — through Braze's REST API, and loads Braze's SDK only for what needs it, such as in-app messages and push notifications. See [Braze hybrid mode](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/hybrid-mode/).

`react_native` and `flutter` device mode covers their Android and iOS builds only. A Flutter app deployed to the web can reach Braze in `cloud` mode only.

`warehouse` is the token a [Reverse ETL source](https://www.rudderstack.com/docs/sources/reverse-etl/) resolves to. Rudder CLI manages the destination’s `warehouse` entry — if the destination is connected to a Reverse ETL source, set `connection_mode.warehouse: cloud` in its spec, or `apply` removes it.

Rudder CLI can also declare the Reverse ETL connection itself, for the types listed under [Supported destinations](https://www.rudderstack.com/docs/rudder-cli/yaml-retl-connections/#supported-destinations) — see [Manage Reverse ETL Connections using Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/retl-connections/).

**Info:** The dashboard additionally offers Braze to AMP and Shopify sources. Rudder CLI doesn&#39;t manage those connections, so `amp` and `shopify` are invalid here.

## Connect a source

An event stream connection to this destination is checked against three rules at `validate` time.

**The source's type must be supported.** A source's type resolves to one of the tokens above before the check — a JavaScript source resolves to `web`, and webhook and server-side SDK sources resolve to `cloud`. Every type an event stream source can resolve to is supported here, so this check always passes.

**The destination config must carry a `connection_mode` entry for that source type.** This lives on the destination spec, not on the [connection spec](https://www.rudderstack.com/docs/rudder-cli/yaml-connections/). Without it:

```text
destination 'braze-prod' config has no 'connection_mode' entry for source type 'web'
```

**A source connecting in `cloud` or `hybrid` mode needs `rest_api_key`.** Device-mode connections don't. Without it:

```text
destination 'braze-prod' config is missing fields required to connect a 'cloud' source: rest_api_key
```

The app identifier keys aren't checked per connection — they're covered by the destination-level rules in [Key dependencies](#key-dependencies).

## Secrets

Rudder CLI treats five keys as secrets: `rest_api_key`, `app_key`, `android_api_key`, `ios_api_key`, and `web_api_key`. Write each one you use as a `{{ .VAR }}` reference and supply the value at apply time:

```yaml
config:
  rest_api_key: "{{ .BRAZE_REST_API_KEY }}"
  app_key: "{{ .BRAZE_APP_KEY }}"
```

```bash
export RUDDER_BRAZE_REST_API_KEY="..."
export RUDDER_BRAZE_APP_KEY="..."
rudder-cli apply

# or
rudder-cli apply --var-file secrets.vars.yaml
```

Note that:

- `rudder-cli import` writes only the secrets the API returns, as `{{ .VAR }}` references, and leaves the others out. Add any secret key it leaves out, then supply the variables before you apply — see [Secrets](https://www.rudderstack.com/docs/rudder-cli/destination-types/#secrets).
- In device and hybrid mode the app identifier keys are embedded in the app or page, so masking them protects your YAML, not the values themselves.

See [How to Use Variable Substitution in Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/variable-substitution/).

## Changes by release

<table>
  <thead>
    <tr>
      <th>Version</th>
      <th>Change</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Breaking:</strong> A <code>null</code> config value, written as <code>key: null</code>, <code>key: ~</code>, or <code>key:</code> with no value, fails <code>validate</code> with <code>'&lt;key&gt;' must not be null; set a value or remove the key</code>. Earlier releases accepted it: a top-level null planned an update on every <code>apply</code>, and a null inside a list item failed at the API.<br><strong>What to do:</strong> Remove the key to leave it unset, or give it a value.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Breaking:</strong> An empty string, <code>&quot;&quot;</code>, on a key that takes one of a fixed set of values fails <code>validate</code> with <code>'&lt;key&gt;' must be one of [...]</code>, unless <code>&quot;&quot;</code> is one of the key&rsquo;s values. Earlier releases accepted it, and the API rejected it at <code>apply</code>.<br><strong>What to do:</strong> Remove the key to leave it unset, or set one of the listed values.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>validate</code> warns when a secret key holds anything but one <code>{{ .VAR }}</code> reference with no default, and when one variable fills two secret keys. It also masks secret values in the lines it prints.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>rudder-cli import</code> writes each secret reference single-quoted, as <code>'{{ .VAR }}'</code>, so a value containing double quotes, like a JSON key file, substitutes as a string. A single quote in a value that fills such a reference is written as <code>''</code>.<br><strong>What to do:</strong> In a spec imported by an earlier release, quote each reference to a JSON value by hand: <code>'{{ .VAR }}'</code>.</td>
    </tr>
    <tr>
      <td>v0.29.0</td>
      <td><strong>Changed:</strong> <code>validate</code> reports a value of the wrong type once per key, such as <code>'email' must be a string</code>, instead of one raw decoding error.</td>
    </tr>
    <tr>
      <td>v0.28.0</td>
      <td><strong>Added:</strong> <code>warehouse</code> source type, for destinations connected to a Reverse ETL source. Set <code>connection_mode.warehouse: cloud</code> for such a destination, or <code>apply</code> removes the entry.</td>
    </tr>
  </tbody>
</table>

For changes across every destination type, see [Destination Type Changes by Release](https://www.rudderstack.com/docs/rudder-cli/destination-types/changes/).

## See more

- [Braze Destination](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/setup-guide/) for finding your keys, data centers, and domain allowlisting
- [Destination Type Reference for Rudder CLI](https://www.rudderstack.com/docs/rudder-cli/destination-types/) for the rules shared across destination types
- [Destination YAML Reference](https://www.rudderstack.com/docs/rudder-cli/yaml-destinations/) for the spec envelope