Skip to content
Infinite Audience Docs

Overview

Infinite Audience API 1.0.0

Section titled “Infinite Audience API 1.0.0”

The primary REST API for Infinite Audience. Authentication: All protected endpoints require a Bearer token in the Authorization header (Authorization: Bearer <access_token>). Obtain an access token by posting your API key to POST /v1/auth/token. API Key Scopes: API keys can be restricted to specific scopes. If a token lacks the required scope for an endpoint, a 403 Forbidden response is returned with a SCOPE_REQUIRED error code. - discovery — Read-only access to count, lookup, segments, demographics, catalogs, and status polling. - purchase — Read-write access to create/update segments and audiences, link campaigns, and execute purchases/deliveries. - account — Full access to self-service API key management, webhook settings, delivery destinations, and billing details.

Operations

Section titled “Operations”
POST
/v1/auth/token
GET
/v1/oauth/authorize
POST
/v1/oauth/token
POST
/v1/oauth/revoke
GET
/.well-known/oauth-authorization-server
GET
/v1/webhook-subscriptions
POST
/v1/webhook-subscriptions
DELETE
/v1/webhook-subscriptions/{id}
GET
/v1/schema/fields
POST
/v1/discovery/count
POST
/v1/discovery/lookup
POST
/v1/discovery/crosstab
POST
/v1/discovery/overlap
GET
/v1/campaigns
POST
/v1/campaigns
GET
/v1/campaigns/{id}
DELETE
/v1/campaigns/{id}
PATCH
/v1/campaigns/{id}
POST
/v1/campaigns/{id}/audiences/{audience_id}
DELETE
/v1/campaigns/{id}/audiences/{audience_id}
GET
/v1/operations
GET
/v1/segments
POST
/v1/segments
GET
/v1/segments/{id}
DELETE
/v1/segments/{id}
PATCH
/v1/segments/{id}
POST
/v1/segments/{id}/count
GET
/v1/segments/{id}/demographics
GET
/v1/segments/{id}/audiences
POST
/v1/segments/{id}/duplicate
DELETE
/v1/segments/bulk
PATCH
/v1/segments/bulk
DELETE
/v1/segments/bulk-delete
POST
/v1/segments/{id}/refresh
POST
/v1/segments/{id}/mappings
POST
/v1/segments/{id}/mappings/cancel
POST
/v1/segments/{id}/upload-failed
POST
/v1/segments/bulk-create
GET
/v1/audiences
POST
/v1/audiences
GET
/v1/audiences/{id}
PUT
/v1/audiences/{id}
DELETE
/v1/audiences/{id}
PATCH
/v1/audiences/{id}
POST
/v1/audiences/{id}/duplicate
POST
/v1/audiences/{id}/count
GET
/v1/audiences/{id}/demographics
POST
/v1/audiences/{id}/refresh
POST
/v1/audiences/{id}/mappings
POST
/v1/audiences/{id}/mappings/cancel
DELETE
/v1/audiences/bulk
PATCH
/v1/audiences/bulk
POST
/v1/audiences/bulk-create
POST
/v1/quote
POST
/v1/deliveries/bulk
GET
/v1/audiences/{id}/deliveries
POST
/v1/audiences/{id}/deliveries
GET
/v1/audiences/{id}/deliveries/{delivery_id}
GET
/v1/match/{id}/deliveries
POST
/v1/match/{id}/deliveries
GET
/v1/deliveries
POST
/v1/match/{id}/analyze
GET
/v1/catalog/fields
POST
/v1/match
GET
/v1/match/file
POST
/v1/match/file
GET
/v1/match/runs
GET
/v1/match/runs/{runId}
GET
/v1/match/file/{matchId}
GET
/v1/workflows/{workflow_run_id}
POST
/v1/workflows/{workflow_run_id}/resume
GET
/v1/account/billing
GET
/v1/account/auto-recharge
PUT
/v1/account/auto-recharge
GET
/v1/account/credits
GET
/v1/account/invoices
POST
/v1/account/payment-method/setup
POST
/v1/account/topups
GET
/v1/account/topups/{requestId}
POST
/v1/account/payment-method/portal
POST
/v1/account/contract/change
POST
/v1/account/contract/cancel
POST
/v1/account/contract/cancellation/revert
GET
/v1/account/usage
GET
/v1/settings/api-keys
POST
/v1/settings/api-keys
DELETE
/v1/settings/api-keys/{id}
GET
/v1/settings/webhook
PUT
/v1/settings/webhook
GET
/v1/settings/notifications
PUT
/v1/settings/notifications
GET
/v1/settings/delivery-destinations
PUT
/v1/settings/delivery-destinations
GET
/v1/settings/billing-preferences
PUT
/v1/settings/billing-preferences
GET
/v1/settings/timezone
PUT
/v1/settings/timezone
GET
/mcp
POST
/mcp
DELETE
/mcp
GET
/.well-known/agent.json
POST
/a2a/tasks
GET
/a2a/tasks/{id}
POST
/a2a/tasks/{id}/cancel
POST
Segment build succeeded WEBHOOK
POST
Segment build failed WEBHOOK
POST
Delivery export completed WEBHOOK
POST
Delivery export failed WEBHOOK

Authentication

Section titled “Authentication”

bearerAuth

Section titled “bearerAuth”

Bearer access token obtained from POST /v1/auth/token. Include in all protected requests as: Authorization: Bearer <access_token>

Security scheme type: http