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

Body

application/json
company
string
required

Any id /companies/{id} takes. It joins the team’s targets if it isn’t one

Required string length: 1 - 64
title
string

The company's name as the report writes it; its own name if left out

Required string length: 1 - 120
playbook
string

The playbook version the writer follows

Maximum string length: 40

Response

Made

id
string
required
company
object
required
title
string
required
status
enum<string>
required
Available options:
draft,
checked
rev
integer
required
problems
integer
required
playbook
string | null
required
saved_by
enum<string>
required
Available options:
key,
member,
agent
created_at
string
required
updated_at
string
required
checked_at
string | null
required
pages
object[]
required
report
object
required
filled
object
required
answers
object
required
cited
object
required
check
object
required
target_added
boolean