> For the complete documentation index, see [llms.txt](https://help.hummingbird.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hummingbird.co/hummingbird-api/how-do-i-generate-api-keys.md).

# How do I generate API keys?

To generate an API key: log into the sandbox/production environment > click on your name on the lower left corner > Settings > Organization tab > API Keys section.

![](/files/DI72oM6ySZ3E0OrdnNqn)

When you create an API key, we prefer it to be associated with an email address that is different from the members of your team. This is the email address where updates and notifications from actions taken by the API are sent. It's normally some sort of group or team alias (<hummingbird-api@hummingbird.co>), but if you want it to be associated with a personal email address, you can also alias your own email address ([yourname+hummingbirdapi@yourcompany.co)](mailto:yourname+hummingbirdapi@yourcompany.co).


---

# 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://help.hummingbird.co/hummingbird-api/how-do-i-generate-api-keys.md?ask=<question>&goal=<endgoal>
```

`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.