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
- Read your calls
Pull calls, summaries, lead scores, callers and follow-ups into your CRM, a sheet or a report.
- Act the moment a call is read
Get a signed message when a call is analyzed, a lead turns hot or a follow-up is due.
- Ask questions from your tools
Send a plain question and get the answer with links to the calls it came from.
- Use your calls in Claude, ChatGPT and more
Connect our MCP server and ask your AI assistant about your calls.
- Send us calls
Post a recording link from any phone system, and we store and read it.
- Automate without code
Apps for n8n, Zapier and Make are coming soon. Until then, their HTTP steps work with the API.
Base URL
Every API route starts with this address. Requests and answers are JSON, and every request needs an API key.
https://listenfox.com/api/public/v1The 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:
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
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
- Authentication: what each scope allows, and OAuth for apps.
- API reference: every route, with examples.
- Webhooks: events, signatures and retries.
- Errors and limits: what can go wrong and how often you can call.
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