Introduction

Find the people and companies to reach, with one API key, billed per record found.

The outbound.dev API finds the people and companies to reach. Search people by a plain-language description or by filters, search companies, list the people who work at a company, and keep searches to run again. Every call draws on a prepaid balance: a search is billed per record it returns, and a search that finds nothing costs nothing.

Quickstart

Create a key, check your balance and run your first search.

Authentication

Keys, scopes and daily spending caps.

Pricing and billing

What each call costs, and how a call is charged.

API reference

Every endpoint, with a playground.

Base URL

https://api.outbound.dev

Every path starts with /v1, the API’s version. The API is served only over HTTPS.

What you can do

Area	What it does	Where to start
People	Search people by a plain-language query, filters or a saved search. Count matches for free.	Search people
Companies	Search companies, name a company from its domain, and list the people who work there.	Search companies
Saved searches	Keep a search under a title and run it again.	Create a saved search
Your account	Your balance and ledger, prices, rate limits, usage and every request of the last 30 days.	Get the balance

Conventions

• Requests and answers are JSON over HTTPS. Send Content-Type: application/json with a body.
• Money is in US dollars, written as an exact six-decimal string such as "0.000500", never as a float.
• Timestamps are ISO 8601 in UTC, such as "2026-11-14T10:02:11.000Z".
• Ids are opaque strings. Never parse or build them.
• Every answer carries an X-Request-Id header, the money headers X-Charged-Usd and X-Balance-Usd, and the rate-limit headers. See Pricing and billing and Rate limits.
• Errors always use one envelope with a stable code. See Errors.

Building with an agent?

Point it at docs.outbound.dev/llms.txt: these docs in plain text, for the agent to read before it calls. The OpenAPI document behind the API reference is at api.outbound.dev/v1/openapi.json.

Need help?

Write to [e-mail] and include the X-Request-Id of the call: it lets us find the exact request.