AdBridge Podcast API
The AdBridge Podcast API is a REST API for building on top of the AdBridge advertising platform. With it you can manage networks, podcasts, host voices, advertisers, campaigns, and the offers and host-voiced creatives that connect them — everything the AdBridge product does, available programmatically.
- Base URL:
https://api.adbridge.ai - All endpoints are under
/v1. - Format: JSON request and response bodies; field names are
snake_case. - Authentication: an API key sent as a bearer token. See Authentication.
Read Core concepts first — it explains the entities (networks, podcasts, voices, advertisers, campaigns, offers, creatives), how they relate, and the two main workflows. The API Reference is organized in that same order.
Quick start
-
Get an API key. A network administrator (or AdBridge) issues you a key. The secret token is shown once at creation — store it securely.
-
Make your first call. List the networks your key can reach:
curl https://api.adbridge.ai/v1/networks \-H "Authorization: Bearer adb_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxx" -
Discover your access. Call
GET /v1/meto see the networks your key is scoped to and at what role, before calling network-scoped endpoints.
How the API is organized
| Resource | What it is |
|---|---|
| Networks | Organizations with an AdBridge account that have rights to represent podcasts and run campaigns. Most resources are nested under a network. |
| Podcasts & Voices | Shows represented by a network and the host voices used to read ads. |
| Advertisers & Campaigns | Brands and the advertising campaigns they run. |
| Offers | A campaign matched to a podcast; accepting one generates a host-voiced creative. |
| Creatives | AdBridge generated ads for a podcast (audio is synthesized asynchronously). |
| Members, Invitations & Service accounts | Who can access a network account, and non-human automation identities (API integrated services). |
| API keys & Webhooks | Self-service credential management and outbound event notifications. |
| Public token flows | Recipient-facing magic-link flows that need no API key. |
Conventions used throughout
- Authentication — bearer API key on every
/v1request. Read more. - Pagination — list endpoints are cursor-based. Read more.
- Errors — every non-2xx response uses one error envelope. Read more.
- Webhooks — subscribe to lifecycle events, verified with an HMAC signature. Read more.
Browse the full API Reference for every endpoint, grouped by resource.