> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/developers/connecting.md).

# Connecting

## Connecting

### Generating an API Key

1. Log in to your BTWB Gym Admin at <https://admin.btwb.com>
2. Navigate to **Gym Tools** in the main menu
3. Select the **Zapier** integration section
4. Click **Create API key** - the new key will be displayed automatically
5. Copy and store the key securely

To view an existing API key later, click **REVEAL KEY** next to it.

### Revoking an API Key

1. Log in to your BTWB Gym Admin at <https://admin.btwb.com>
2. Navigate to **Gym Tools** > **Zapier**
3. Find the API key you want to revoke
4. Click the **delete** icon next to the key
5. Confirm revocation in the dialog

{% hint style="warning" %}
Revoking an API key is permanent and immediate. Any integrations using that key will stop working.
{% endhint %}

### Using with Zapier

To use the BTWB Zapier integration:

1. Log in to your Zapier account at [zapier.com](https://zapier.com)
2. Search for "BTWB" in the app directory
3. Connect your BTWB Gym account using an API key
4. Create Zaps using the available triggers

For detailed instructions on creating Zaps and configuring triggers, see:

* [How to Create a Zap](https://help.zapier.com/hc/en-us/articles/8496309697421-Create-Zaps)
* [Understanding Triggers](https://help.zapier.com/hc/en-us/articles/8496309697421-Create-Zaps#h_01HNGXXP42VBCCP8QB5YS0JXJZ)


---

# 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://btwb.gitbook.io/btwb/developers/connecting.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.