> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/integration/braze.md).

# Braze

This section outlines the partnership between Braze and Open Loyalty.

The Braze and Open Loyalty integration allows you to sync loyalty data—such as points balance, tier changes, and expiry warnings—directly into Braze in real-time. This enables you to trigger personalized messages (Email, Push, SMS) immediately when a user's loyalty status changes.

### About this integration

This integration uses **Braze Data Transformations** to capture webhooks from Open Loyalty and map them to Braze User Profiles.

* **Real-time Updates:** Push loyalty events (Points Earned, Tier Upgrades) to Braze instantly.
* **Personalization:** Use loyalty attributes (Current Balance, Next Tier Name) in your Braze templates.
* **Bi-directional:** Update Open Loyalty customer custom attributes based on Braze engagement data.

### Prerequisites

| Prerequisite              | Description                                                                                                                                                                               |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Open Loyalty Account      | You must be an Admin on an Open Loyalty Tenant.                                                                                                                                           |
| Open Loyalty REST API Key | <p>An Open Loyalty REST API Key (for integrations where data is sent from Braze to Open Loyalty)</p><p>Create this in <strong>Settings > Admins ></strong> <strong>API Keys</strong>.</p> |
| Braze REST API Key        | <p>A Braze REST API key with <code>users.track</code> permissions.<br><br>Create this in <strong>Settings</strong> > <strong>API Keys</strong>.</p>                                       |
| Braze Data Transformation | Access to the "Data Settings" tab in Braze to configure webhook listeners.                                                                                                                |

### Limitations

**Braze**

Using Braze Data Transformations involves specific rate limits, allowing up to 1,000 incoming requests per minute per workspace. This limit can be increased under a paid plan.

**Open Loyalty**

Open Loyalty imposes its own rate limits (usually around 1,500 incoming requests per second), which are detailed further in [Environments Capabilities](/technical-guide/api-fundamentals/environments-capabilities.md). It's essential to consider these limitations when planning an integration to ensure efficient data flow and prevent disruptions.

### Integration Guides

Select the direction of data flow you wish to configure:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Syncing Open Loyalty Events to Braze</strong></td><td>Learn how to capture any Open Loyalty webhook (Points, Tiers, etc.) and map it to Braze User Events.</td><td><a href="/technical-guide/integration/braze/open-loyalty-to-braze.md">Open Loyalty to Braze</a></td></tr><tr><td><strong>Updating Open Loyalty from Braze</strong></td><td>Learn how to update member attributes and labels in Open Loyalty using Braze Webhooks.</td><td><a href="/technical-guide/integration/braze/braze-to-open-loyalty.md">Braze to Open Loyalty</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/technical-guide/integration/braze.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.