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

# API key management

To optimize your experience and interaction with Yad Finance's platform, it's essential to understand our API key management system. This key not only enhances your access capabilities but also ensures seamless integration for both developmental and production purposes. Below are some crucial details about our API key management:

* **Limited access without a key**: While you can make requests without an API key, the number of requests per second will be limited. This is ideal for developmental and testing phases but not recommended for full-scale production.
* **Obtaining a key**: To get your API access key, simply reach out to us at <partners@yad.finance>.
* **Key integration**: Ensure that the provided key is added to the header of each request using the parameter {"X-API-Key": "\<key>"}.

For partnership inquiries or any other questions, don't hesitate to contact us at <partners@yad.finance>.


---

# 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://docs.yad.finance/integration-guides/widget/api-key-management.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.