Using the REST API

This page is the 5-minute overview. For the complete endpoint reference (every resource, every parameter, every error), head to /docs/api.

Key concepts

Mint an API key

Generate keys from Settings → API keys. Keys are workspace-scoped and shown exactly once at creation - store them in 1Password / AWS Secrets Manager / Doppler, never in your repo.

Quick example: list agents

The simplest possible call - list the agents in your workspace. Copy/paste and run:

curl https://flooai.com/api/v1/agents \
  -H "Authorization: Bearer $FLOO_API_KEY"

You will get something like this back:

{
  "agents": [
    {
      "id": "agt_2k9f1a",
      "name": "Sales Receptionist",
      "voice_provider": "cartesia/sonic-3",
      "created_at": "2026-05-01T12: 00: 00Z"
    }
  ]
}

That's the whole shape: a top-level key matching the resource, payload underneath. Errors return { "error": "...", "code"?: "..." } with a 4xx/5xx HTTP status.

What you can build with the API

• Provision agents from your app - let your end users create their own voice agents inside your product (whitelabel).
• Outbound campaigns - POST a list of phone numbers and Floo dials them sequentially (or in parallel) and streams transcripts back.
• CRM sync - subscribe to call.completed webhooks and push transcripts + outcomes into HubSpot, Salesforce, or your data warehouse.
• Dynamic KBs - programmatically add knowledge from your existing CMS so the agent stays in sync with your help center.