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

# The partner API

fija provides an **API** for its partners.

**Technical Description of our API** is available [here](/docs/overview/the-partner-api/interface-documentation.md).

Via the API the partners can:

* lookup which strategies are available to the partner
* receive all necessary information about the fija strategies, incl. deposit/withdrawal functions and smart contract addresses of the respective partner vault
* receive information about the performance of a strategies, e.g. APYs and Safety Score

The **following information** about the strategies is **available via the partner API**:

* Strategy Name
* APY (current APY, weekly APY, monthly APY, lifetime APY)
* Safety Score
* Strategy Description
* Strategist
* Portfolio of the strategy
* Key information document (BIB)
* Token T\&Cs (Emissionsbedingungen)


---

# 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://fija.gitbook.io/docs/overview/the-partner-api.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.