> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/manager/pages/api-key.md).

# API Key

The Bloom API lets you drive trading and token launches programmatically using a personal API key:

* [**Swaps**](https://dev.bloombot.app/api-reference/swap): execute buys and sells across one or more of your wallets — or, with `wallets` omitted, across your default trading wallets — with optional take-profit, stop-loss, trailing, time-based, and dev-sell auto-orders.
* [**Token deploys**](https://dev.bloombot.app/api-reference/deploy): launch new tokens on supported DEXes (pump.fun, Bags, Bonk), with bundled buys and post-deploy distributions. Deploys are Solana-only.
* [**Wallets**](https://dev.bloombot.app/api-reference/wallets): list the wallets on the account, so an integration can discover addresses instead of asking for them.

***

### API Technical Docs

{% embed url="<https://dev.bloombot.app/introduction>" %}

***

### Create an API key

{% stepper %}
{% step %}

#### Open API Keys

Tap your username, then tap **API Keys**.

<figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FdlLLBPizKy1AmPhQqvN8%2Fapi%201.png?alt=media&amp;token=9f72c7c2-6336-4cbf-a77e-beb7a435d0d3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Create a key

The **API Keys** dialog lists your active keys. Select the chain for the new key, then tap **Create API Key**.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FuvGozpNnXYfq3g77Qcbi%2Fapi%202.png?alt=media&amp;token=46c6b78a-233d-4841-aee2-5c981881df01" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Name the key

Enter a name for the key. Complete the prompts to create it.

<div align="left"><figure><img src="https://373591576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMnkwltEDWRRlh7lLk05b%2Fuploads%2FFnG0fff0z7ua466SiChP%2Fapi%203.png?alt=media&amp;token=1847c855-a2b3-4181-bd32-9fb881136bb5" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Integration

Read the technical docs to integrate the Bloom engine into your code:

{% embed url="<https://dev.bloombot.app/introduction>" %}
{% endstep %}
{% endstepper %}


---

# 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.bloombot.app/manager/pages/api-key.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.