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

Body

application/json
rival
string

A company any /companies/{id} takes

Required string length: 1 - 64
name
string

Or, for a company PodData doesn't hold, its name

Required string length: 2 - 120
domain
string

And its own domain, which goes in as a proposed link

Required string length: 3 - 253
why
string

What makes it a rival, in a sentence

Required string length: 3 - 500
evidence
string

The page that shows they compete

Required string length: 8 - 2000

Response

Already its rival, proposed, confirmed or struck: as it stands

rival
object
required
state
enum<string>
required
Available options:
proposed,
confirmed,
struck
evidence
string | null
required
decided_at
string | null
required
waits_for
enum<string> | null
required
Available options:
team,
poddata,
null