Skip to main content
GET
curl, made-up values
MCP tool: company_ads, on PodData’s MCP server at https://api.poddata.ai/mcp, does what this route does, with the same key. See The MCP server.

Authorizations

Authorization
string
header
required

An API key, sent as Authorization: Bearer pd_live_…. Someone on your team makes one in the workspace, Settings › API keys; it's shown once. Staging's keys start with pd_test_.

Path Parameters

id
string
required
Maximum string length: 64

Query Parameters

source
string

The ad library, by catalog id: meta-ad-library if left out

Required string length: 1 - 64
on
string<date>

The day to count the ads running on, by each brand's last pull on or before it: today if left out

vs
string<date>

The earlier day to compare it with: four weeks before on if left out

state
enum<string>

Which ads: running on on (the default), started, stopped or not seen since between vs and on, or all

Available options:
running,
started,
stopped,
not_seen,
all
platform
string

Only those running on one platform: facebook, instagram, messenger, audience_network, threads

Maximum string length: 40
limit
integer

How many a page: 50 if left out

Required range: 1 <= x <= 100
cursor
string
Maximum string length: 200

Response

A brand's ads on a day

company
object
required
source
string
required
on
string
required
vs
string
required
pages
integer
required
pulls
object[]
required
on_pull
string | null
required
vs_pull
string | null
required
complete
boolean | null
required
counts
object
required
cannot
string | null
required
data
object[]
required
next
string | null
required