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

# FLORA API platform

The rules every FLORA API request follows: API key authentication, error codes, safe retries with idempotency keys, and signed webhooks.

These pages cover the behavior shared by every FLORA API endpoint. Read Authentication before your first request, and Errors and Idempotency before you put a script into production.

* [Authentication](https://docs.flora.ai/api/platform/authentication.md): create API keys, choose their workspaces and permissions, rotate and revoke them.
* [Errors](https://docs.flora.ai/api/platform/errors.md): every error code, what causes it, and whether to retry.
* [Idempotency](https://docs.flora.ai/api/platform/idempotency.md): retry with the `Idempotency-Key` header or a Technique run's `idempotency_key` without duplicate runs.
* [Webhooks](https://docs.flora.ai/api/platform/webhooks.md): get a signed callback when a run finishes instead of polling.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/api/platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
