Skip to main content
For a diligence, PodData reads public sources about a company through the links a person on your team has confirmed: its domain, its places, its listings and accounts, its numbers at registries. Three kinds of thing come back, each with its own day and its page on the source’s site: Pass a source’s id below as source to narrow a list to it. The number tools count records and signals for you, beside a company’s confirmed rivals.

What’s been read for a company

  1. Every source, live. GET /integrations (list_integrations) lists each source with when it last ran and how much PodData holds from it; GET /integrations/{id}/items (source_items) lists what it holds, item by item.
  2. For one of your targets. GET /targets/{company}/coverage (target_coverage) says, source by source, whether it has read the target and its confirmed rivals, what it holds and over which days, and which kind of link a source still waits on.
  3. As files. A target’s folder gives a CSV a source and kind: see A target’s folder. Where a source’s file is held back, held says why, and its rows read as JSON.
A source reads a company only through a link of the kind it needs: a review site through the company’s listing there, a registry through its number. Confirming the right links is what makes a source read. Data your team reads through its own licence to a vendor is by request today.

Every source production reads

Company filings

Health

Food and product safety

Labour and building

Telecom

Gaming

News, wires and deals

Reviews

Retail

Social

Ads

Search interest

Shows and video