Prospex documentation

Prospex holds a picture of every company on the Swiss commercial register: what it does, where it is, how big it is, and what has happened to it lately. You work in lists. A list is built from a description (a ranked set of companies worth selling to), imported, or made of the companies you follow. Monitoring tells you what changed on any of them. Outreach, run on a list, qualifies a company, researches it against public sources and drafts an opener grounded in that evidence.

Each of the three has a surface a program can reach.

What is reachable from outside the browser

SurfaceCredentialWhat it gives you
List feed A token in the URL One list's companies as JSON or CSV, with the list's own reasons on every row.
List signal feed A token in the URL One list's signals as JSON or CSV, using its current companies and topics.
Outreach feed A token in the URL The outreach of one list: qualification, research with its evidence, and the opener state.
Outreach API A scoped bearer key Add companies, start research, claim a step, approve a named revision.
Webhooks A signing secret Signed delivery when research lands, an opener needs approval, or a cycle finishes.
HubSpot, Attio and Pipedrive OAuth Push companies out, mirror your CRM back in, fill blank fields on records you already had.

Where to start

Getting started

What a credential is, how a response is shaped, and what is counted.

Integrations

The CRMs Prospex connects to, the automation tools people arrive from, and the command line and agent skill.

API reference

Every field, parameter, status and stable token, generated from the code.