Skip to main content
GET
curl, made-up values
MCP tool: numbers_timeline, 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

from
string<date>

The first day, by each event's own day: all of them if left out

to
string<date>

The last day: today if left out

kinds
string

A comma list of what to keep: breach, recall, warning, award, licence, deal, case, story and the like. All of them if left out

Maximum string length: 200
limit
integer

How many events, newest first: 50 if left out

Required range: 1 <= x <= 200
format
enum<string>

csv: the answer as a file, its rows under its columns, or with part=figures its named figures. json: the answer, the default

Available options:
json,
csv
Example:

"csv"

part
enum<string>

With format=csv: rows (the default), the table behind the chart, a row each with a column for each of its columns; or figures, a row each with its label, value, unit, company, n and interval

Available options:
rows,
figures
Example:

"figures"

Response

A row an event

numbers
enum<string>
required
Available options:
rating,
rating_by_link,
rating_rivals,
rating_windows,
complaints,
series,
timeline,
ads,
ads_weeks,
site,
site_changes
company
object
required
params
object
required
figures
object[]
required
columns
object[]
required
rows
object[]
required
evidence
object
required
basis
object
required
computed_at
string
required