> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/workspace-settings/integrations/flowerbuddy-api.md).

# FlowerBuddy API

The **FlowerBuddy API** tab is available on eligible workspaces that need an external integration to create, read, or edit FlowerBuddy events. It shows whether an API key is active and provides the entry point for managing that key.

An API key is a credential. Treat it like a password: share it only with the trusted system or person that needs it, and replace it when the integration no longer needs the existing key.

The FlowerBuddy API tab shows the workspace API state without displaying credential material.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-ba7995d333db564dac0cdd19ab1702a424afb8e8%2F12-flowerbuddy-api.png?alt=media" alt="FlowerBuddy API tab showing that no API key has been generated, with Generate API Key and FlowerBuddy API Docs buttons." width="550"><figcaption></figcaption></figure></div>

Endpoint reference is maintained separately in the [FlowerBuddy API documentation](https://api.flowerbuddy.co/v1/docs/). Use [Manage FlowerBuddy API keys](/reference/workspace-settings/integrations/flowerbuddy-api/manage-flowerbuddy-api-keys.md) for the key lifecycle.

## In this section

* [Manage FlowerBuddy API keys](/reference/workspace-settings/integrations/flowerbuddy-api/manage-flowerbuddy-api-keys.md)