> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/braze/installation-guide.md).
# Installation Guide
See the steps below
1. Log into **Braze**
2. Once logged in head to 'Settings' on the sidebar menu, then 'API and Identifiers'
3. Once in **API and Identifiers UI** click on **API Keys** tab and then **'Create API Key'**
4. Set your **Name** and select **Custom Attributes, Events, Segments and User Data** and click **Create API Key**
5. Save the key somewhere secure such as a password manager ready to use in ZAP POST.
6. Copy your REST endpoint too, this will also be required for your account setup.
7. Once you have your API key and Base URL, log into [ZAP-POST](https://app.zappost.com)
8. From the dashboard click on the **integrations** tile
9. Here you will see a tile to add Braze
10. Add the **API Key** that was created in Braze and the **Endpoint URL** that was copied
11. Click **Connect**
12. If the correct credentials have been provided, you see a **confirmation**
13. You are all set! Your Braze account is integrated with ZAP-POST. You will now be able to use ZAP POST Events in your Braze account. In order to ingest Segment data see our Use case how-to guide
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://userguide.zappost.com/zap-integrations/zap-post-integrations/braze/installation-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.