Flourish External API Overview
External API documentation connects custom applications to Flourish. Covers API keys, webhooks, security, and MCP server. Admins plan access; developers implement. Protect all credentials.
Use the External API documentation to connect custom applications and automations to Flourish. This category covers API key administration, event-driven webhooks, webhook security, and the Flourish MCP server.
API access should be planned and managed by an authorized administrator and implemented by a developer who understands the data and workflows being connected.
API Documentation: https://api-docs.flourishsoftware.com/
Choose where to start
If you need to | Start here |
Understand how API keys are managed | |
Generate or reset an API key | |
Receive event notifications | |
Verify webhook requests | |
Connect an LLM through the Flourish MCP server |
Protect credentials and data
- Treat API keys and webhook secrets as sensitive credentials.
- Store credentials outside source code and public documentation.
- Give access only to the people and systems that require it.
- Plan how a reset or rotation will affect connected systems before changing a credential.
- Test integrations with controlled data and review their effects before using them in production workflows.
Get implementation details
Use the API reference or endpoint documentation provided for your Flourish implementation for request fields, responses, supported operations, and current limits. If the available documentation does not answer an implementation question, contact Flourish Support before assuming behavior.
How did we do?
Connecting to Flourish with an LLM using our MCP Server
