> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/partners/partner-dashboard/creating-api-keys.md).

# Creating API keys

A Branch API key lets a POS system or online store send payments to SensePass for one location.

1. Open the location's three-dot menu and select **Branch API**, or open **Developer** > **Branch API** in the left menu.
2. Click **+ New**. The **Create Branch Api Key** window opens.
3. Enter a **Name** for the key, for example *Online Ordering*, and check the **Location**.
4. In **POS Vendor**, select the system that will use the key. Type in the list to search, for example **API**.
5. Select **Commit Required** or **Commit Not Required**. See the note below.
6. Click **Save**. The key appears in the list. Click the copy icon next to the key to copy it.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FJUCrCI7ob877iyaqZFNh%2Fp-branch-filled.png?alt=media" alt="Create Branch Api Key window"><figcaption><p>Create Branch Api Key window</p></figcaption></figure>

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2Fl6XDa4X680XcsiPaifYF%2Fp-branch-created.png?alt=media" alt="The new key in the Branch API list (key hidden)"><figcaption><p>The new key in the Branch API list (key hidden)</p></figcaption></figure>

{% hint style="info" %}
**Note:** With **Commit Required**, the integration must confirm each payment with a Payment Commit call. See <https://docs.sensepass.com/sensepay/transaction-api/payment-flows/payment-commit>.
{% endhint %}

{% hint style="warning" %}
**Important:** An API key gives access to the location's payments. Share it only with the developer who sets up the integration, and never by unsecured email or chat.
{% endhint %}


---

# 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://docs.sensepass.com/sensepay/partners/partner-dashboard/creating-api-keys.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.
