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

# Authentication

&#x20;  **a)** **API Key Generation:** Users can generate their API keys by logging into their Flickrz account and navigating to the API settings section. They can then create a new API key and securely store it for authentication purposes.

&#x20;  **b)** **API Key Usage:** Once users obtain their API key, they must include it in the request headers of API calls to authenticate their requests. The API key should be included in the Authorization header as a Bearer token.

Authentication is required for certain endpoints. The Flickerz API currently supports API key authentication. Please include your API key in the request headers as follows:

```
Authorization: Bearer YOUR_API_KEY 
```


---

# 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:

```
GET https://flickrz.gitbook.io/whitepaper-flickrz/api-documentation/authentication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
