API v1 · 2026-10-14
Build on Listener
One API for every Listener workspace: shows, analytics, episodes, clusters, campaigns and reports. The same numbers the apps show, over REST, signed webhooks and MCP.
- 1Create a key in Settings → Developers in Listener Networks or Listener.
- 2Export it as
LISTENER_API_KEYand callGET /v1/me. - 3Read shows and reach, then subscribe to webhooks for changes.
curl https://api.listener.com/v1/me \
-H "Authorization: Bearer $LISTENER_API_KEY"Response 200
{
"object": "workspace",
"kind": "network",
"network_name": "Northwind Audio",
"show_count": 12,
"shows": [
{
"id": "8sQe1v0x2kTq",
"name": "Dugout Daily"
}
],
"credential": {
"type": "api_key",
"scopes": ["workspace:read"]
}
}Explore the platform
Everything you need to read your data, act on it and hear about changes.
GuidesAccounts, authentication, pagination, time windows and the metric definitions behind every number.API referenceEvery endpoint with parameters, response schemas, samples in curl, Node and Python, and a Try it console.WebhooksSigned, retried notifications when campaigns, clusters, episodes or data change. Or poll the Events API.OAuth 2.0Let Listener users connect your app with “Sign in with Listener”: authorization code with PKCE, scoped and revocable.MCP serverConnect Claude, ChatGPT or Cursor to a workspace. Same tools, same numbers, guarded writes.SDKsSoonTyped clients for TypeScript and Python, generated from the OpenAPI document.