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

The report's id, dlr_…

Maximum string length: 64

Body

application/json
message
string

What to change, in a sentence or two. Left out, the run writes a first draft

Required string length: 1 - 2000

Response

Started: it runs in the background. Read it with GET /v1/diligence-runs/{id}

id
string
required

drn_…

report
string
required
company
string
required
kind
enum<string>
required
Available options:
write,
change
message
string | null
required

What a person asked for, on a change

status
enum<string>
required
Available options:
queued,
running,
waiting,
checking,
done,
stopped,
capped,
refused,
failed
why
string | null
required

Why it waits or ended, in a sentence

model
string
required
playbook
string
required

The playbook's version

usd
number
required

What its turns have cost so far, in dollars

cap_usd
number
required

What it may spend, in dollars: the cap on a run

turns
integer
required
agents
object[]
required
refusals
string[] | null
required

What the check last refused, each in a sentence

started_by
object
required

Who started it. A key or an assistant counts toward the plan's runs a day; the workspace doesn't

created_at
string
required
updated_at
string
required
ended_at
string | null
required