Spotify Monthly Listeners

Running music outreach from your own tools

Updated 5 October 2026 · 2 min read

If you manage a roster, the bottleneck is rarely the pitch — it is the process around it. Moving lists, verifying them, launching campaigns and collecting results by hand does not scale past a few artists.

What an outreach API should expose

The useful surface is small: import and verify contacts, create campaigns, read results, receive events. Everything else is a dashboard concern.

  • Contacts: list your own lists, import and verify in one call.
  • Templates: create and list the copy your team reuses.
  • Campaigns: create one per list from your own tooling, with the normal send gates applied.
  • Results: aggregated and per-campaign statistics.
  • Events: signed webhooks so your CRM hears about launches and replies.

Safety and scoping

Keys should be scoped to a single account and shown once, stored only as a hash. A key must never expose another client’s data, and programmatic creation must go through the same entitlement, verification and sender checks as the interface — otherwise the API becomes the way to bypass your own rules.

Events instead of polling

Signed webhooks let your system react to a launched campaign or a new reply without polling. Verify the HMAC signature over the raw body before parsing, and treat delivery as best-effort: deduplicate on your side and reconcile counts periodically rather than assuming exactly-once delivery.

How ours works

Every account gets scoped `ask_live_` keys with leads, templates, campaigns, stats, replies and verification endpoints plus five signed webhook events. Full documentation, including the raw-body verification snippet and the honest limits, is published at /docs/api.

A sensible first automation

Do not automate the pitch. Automate the bookkeeping around it. The highest-value first integration is usually the simplest: push every reply your outreach receives into the CRM or spreadsheet where you already track relationships, so a response is never lost in an inbox.

The second is a monthly reconciliation: pull campaign counts and listener figures on a schedule and append a dated row per artist. That record is what turns a roster from a collection of anecdotes into something you can make decisions with, and it is the least glamorous and most useful thing an API can do for a label.

Frequently asked questions

Do I need a developer?

For the API, yes — or an automation platform. The workspace interface covers everything the API does, for a single artist.

Can the API bypass verification?

It must not. In our implementation, programmatic campaign creation runs the same verification, entitlement and sender checks as the interface.

Are webhooks reliable?

Treat them as notifications rather than a guaranteed delivery log. Reconcile important state by reading the API, and deduplicate events yourself.

Keep reading