API
Automate your go-to-market with one API key
One key instead of thirty. Use it in your own workflow, or ship it inside your product.
Your whole go-to-market, behind one key
The agent behind the Retriever app, called from your scripts.
Find companies
On filters, or on any signal you can describe.
Find contacts
Decision makers, with verified email and phone.
Find content
Viral posts, ads, and the creators behind them.
Track signals
Hiring, funding, tech stack, ads, reviews.
Sequence them
Draft, enroll, watch the replies land.
Connect your CRM
HubSpot, Salesforce and more, coming soon.
What can you call in the API?
Four surfaces, one key.
| Surface | What it does | Calls |
|---|---|---|
| Runs | A full mission: it sources, qualifies, and publishes a table. | POST /v1/runsGET /v1/runs/{id} |
| Go | One fact from the web, typed against your own JSON schema. | POST /v1/go/runPOST /v1/go/runs |
| Services | One enrichment at a time: email, phone, job posts, tech stack. | GET /servicesPOST /services/{name} |
| Credits | What is left on the key. | GET /credits |
How do you make a first call?
A key from the app settings, one call, then poll.
export RETRIEVER_API_URL="https://api.retriever.run"
export RETRIEVER_API_KEY="ret_live_..."
curl -s -X POST "$RETRIEVER_API_URL/v1/runs" \
-H "Authorization: Bearer $RETRIEVER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "Find 20 B2B SaaS companies in France hiring engineers, with their website.",
"output": { "type": "tables", "tables": [{ "key": "companies" }] }
}'You get a 202 and a run id. Poll it, then read the table or export it. Same walkthrough in Node and Python in the documentation.
What teams automate with it
Enrich a CRM list
Import accounts, get the decision maker, export as CSV.
Sync your exclusions
Customers and engaged contacts, never sourced again.
Pin the output shape
Declare the columns, get that exact table.
Serve several clients
One key per organization, or one workspace each.
Reference
The full reference lives in the API documentation
Endpoints, error codes, rate limits, recipes and the OpenAPI file.
Open docs.retriever.run →Frequently asked questions
Keys, runs, costs and where the full reference lives.
Where do I get an API key?
In the app, under Settings then API keys. It starts with ret_live_ and is shown once. The same key opens the API and the MCP server.
Is a run synchronous?
No. POST /v1/runs answers 202 with a run id, and you poll GET /v1/runs/{id} until it is done, honouring Retry-After. Go has a synchronous variant for short searches.
What does a call cost?
Credits, per call. GET /services/{name} returns the cost of a service, GET /credits returns the balance.
Is there an OpenAPI specification?
Yes, in the API documentation at docs.retriever.run, with the error codes, the rate limits and the pagination rules.