> For the complete documentation index, see [llms.txt](https://evenings.gitbook.io/evenings-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evenings.gitbook.io/evenings-api/api/api-keys.md). # API Keys ## Obtaining an API Key The Evenings API is currently in development. To ensure optimal support and understand usage patterns, we require users to request an API key. To obtain your key, please contact our team at with a brief description of your intended API use case. ## Authentication 1. Authentication is implemented using the Bearer token method. 2. Include the API key in the Authorization header like so: `Authorization: Bearer YOUR_API_KEY`. Replace `YOUR_API_KEY` with the key you received. ## Managing Your API Key ### Locating Your API Key Once your API key request has been approved, you can access your key through your Account dashboard. From there, you can copy the key or generate a new one if needed.
### API Key Regeneration For security purposes, you may occasionally need to regenerate your API key. This functionality is available within your Account settings. Please note that regenerating your key will invalidate the previous one, requiring you to update any applications or scripts using the API.
## Questions If you have any questions or feedback, please contact us at [**contact@evenings.email**](mailto:contact@evenings.email). --- # 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://evenings.gitbook.io/evenings-api/api/api-keys.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.