A people-research endpoint for your workflows
POST a person's name and company; poll until complete; get back a structured briefing in markdown — background from their public LinkedIn profile, recent public web results, and the key owner's own email history. Call it from n8n, Make, Zapier, a CRM automation, or an agent.
Built for developers and ops people wiring people research into CRMs, automation tools, and AI agents.
No credit card. One credit per dossier, about 60 seconds per run.
Two requests
Create, then fetch. Keys are created in Settings → API Keys and work on every plan, including the free credits.
curl -X POST https://rundossier.com/api/v1/dossiers \
-H "Authorization: Bearer dsk_live_your_key" \
-H "Content-Type: application/json" \
-d '{"subject_name": "Sarah Chen", "context": "VP of Engineering at TechCorp"}'
# → {"id": "b3f1c2a4-…", "status": "pending"}
curl https://rundossier.com/api/v1/dossiers/b3f1c2a4-… \
-H "Authorization: Bearer dsk_live_your_key"
# → {"id": "…", "status": "complete", "result_markdown": "# Dossier - Sarah Chen …", …}The subject is a person — subject_name is their full name and context carries the company or title your system already knows. No LinkedIn URL is required; discovery is part of the request.
What comes back
result_markdown is the full dossier — summary, professional background, relationship context, talking points, quick facts — ready to store as a note or render as-is. This is its opening section:
Sarah Chen is a seasoned engineering leader with over 15 years of experience building and scaling technology teams at high-growth companies. Currently VP of Engineering at TechCorp, she oversees a team of 120+ engineers across platform, infrastructure, and product engineering. Previously held senior roles at Stripe and Google. Known for her expertise in distributed systems and building engineering culture.
Sarah Chen and TechCorp are fictional; the structure and depth are what a real run produces. Read the full example dossier.
Where it fits
CRM enrichment on a trigger
When a contact is created or a meeting is booked, create a dossier from the contact's name and company, wait, then write result_markdown into a note on the record. The rep opens the CRM and the briefing is already there.
Calendar-driven briefings
A scheduled workflow reads tomorrow's external attendees, runs one request per person, and posts the summaries to Slack or email the evening before. RunDossier itself is pull, not push — the workflow supplies the trigger.
A tool for an agent
Give an AI agent a “who is this person” tool without stitching together profile discovery, web search, and summarization yourself. Responses are JSON with snake_case fields; docs are also served as plain markdown at /docs/api.md for agents to read directly.
The facts you will check
| Base URL | https://rundossier.com/api/v1 |
|---|---|
| Auth | Authorization: Bearer dsk_live_… (personal key, Settings → API Keys) |
| Create | POST /dossiers { subject_name, context? } → 201 { id, status: pending } |
| Fetch | GET /dossiers/{id} → status pending | processing | awaiting_selection | complete | error |
| Disambiguate | POST /dossiers/{id}/select { selected_url } — null cancels and refunds |
| Balance | GET /credits |
| Rate limits | 10 writes/min and 60 reads/min per key; 30 req/60s per IP pre-auth; 429 + Retry-After |
| Cost | 1 credit per dossier, same balance as the web app; 402 at zero |
| Spec | OpenAPI 3.1 at /api/v1/openapi.json; markdown docs at /docs/api.md |
Full reference, with JavaScript and Python examples: /docs/api.
Frequently asked questions
Is there a native n8n, Make, or Zapier integration?
Not yet. The API is plain REST with bearer-key auth and JSON bodies, so it works from the HTTP Request node in n8n and Make and from Zapier's Webhooks action today: one request to create, a short wait, then one request to fetch. The OpenAPI 3.1 spec at /api/v1/openapi.json can also generate a client in most languages.
What input does the API take?
A subject_name (the person's full name) and an optional context string such as a title and company. Context is what disambiguates a common name — pass it whenever your CRM has it. The API researches people; a company name as the subject will not find a profile.
How long does a request take, and how do I know it is done?
Create returns immediately with status pending. Poll GET /api/v1/dossiers/{id} every 5–10 seconds until status is complete or error; most dossiers finish in about 90 seconds. There is no webhook yet, so a short polling loop or a delayed second step in your workflow is the pattern.
What happens when a name matches several people?
The dossier returns status awaiting_selection with a candidate_profiles array (name, headline, location, profile URL). POST the chosen url to /api/v1/dossiers/{id}/select to continue, or null to cancel and refund the credit. An agent can decide using the context it already has.
What does it cost, and are there rate limits?
One credit per dossier from the key owner's balance — the same credits as the web app, on every plan including the free 3 credits. Writes are limited to 10 per minute per key and reads to 60 per minute; a 429 carries a Retry-After header.
Can I include my own email history in API-generated dossiers?
Yes. If the account that owns the API key has connected Gmail, dossiers created through the API include the same relationship section the web app produces. Email is analyzed during generation and never stored.
Create a key and make the first call
Sign up, open Settings → API Keys, and run the two requests above on your free credits. No card, no separate API tier.
Related reading
RunDossier is a meeting-preparation tool for professional use. It compiles publicly available professional information and, with your permission, your own email history. It is not a consumer reporting agency and dossiers are not consumer reports — see the Terms of Service for permitted use.