Developer docs: Overview

Build on your calls.

The ListenFox API gives your own code the same calls, callers, follow-ups and answers you see in the app. Webhooks tell your systems when something happens, and the MCP server lets AI assistants read your calls.

What you can build

Base URL

Every API route starts with this address. Requests and answers are JSON, and every request needs an API key.

Base URL
https://listenfox.com/api/public/v1

The MCP server for AI assistants lives at https://listenfox.com/api/mcp. See MCP server.

Quick start

1. Create an API key

In ListenFox, open Settings → API keys and click Create a key. Give it a name, pick Read only for now, and copy the key. It starts with lf_live_ and is shown only once. You need the owner or admin role. Step by step

2. Check that it works

Save the key in an environment variable, then ask who it belongs to:

Terminal
export LISTENFOX_API_KEY="lf_live_..."

curl "https://listenfox.com/api/public/v1/me" \
  -H "Authorization: Bearer $LISTENFOX_API_KEY"

You get your workspace name and the key’s scopes back. A 401 means the key was copied wrong or has been revoked.

3. Get your hot leads from the last week

Terminal
curl "https://listenfox.com/api/public/v1/calls?lead_band=hot&since=2026-10-12T00:00:00Z" \
  -H "Authorization: Bearer $LISTENFOX_API_KEY"

Each call comes with its summary, lead score, caller and a link that opens it in ListenFox. When there are more calls than fit on one page, pass the next_cursor from the answer as cursor to get the next page.

Where to go next

CreditsReading data is free. Two things use credits, exactly as they do in the app: analyzing a call (2 credits on the Standard effort level, 1 on Quick, 4 on Deep, per started 5 minutes), and asking a question (1 Ask credit, 3 on Deep; AI credits once those run out). The reference marks these routes “Uses credits”. How credits work