What is the Pursuit Accounts API?

Quick Answer

The Pursuit Accounts API returns Pursuit's public sector account universe as filterable, paginated data. Any customer with an API key can call GET /v1/accounts and pull the same account reference data Pursuit's signals run on into Clay, a spreadsheet, or a partner tool. Full endpoint reference lives in the API docs at https://api.pursuit.us/v1/docs.

What This Is

Pursuit maintains reference data on the public sector entities your team sells to: name, website, state, population, account type, and geography. The Accounts API exposes that universe over HTTP so your own stack can ask for it. Before this release, getting the universe into an outside tool meant asking Pursuit for a one-off export. Now it is a documented endpoint you query on demand, with the same data behind it.

How It Works

Search by the fields that matter

GET /v1/accounts filters on name, website, state, population range, account type, and geography, including a radius search that returns every account within a set distance of a latitude and longitude. Results are paginated, so a filter matching thousands of accounts comes back in ordered pages instead of one payload.

Find out what is filterable

GET /v1/accounts/sum-lev-groups returns the account-type groups (Counties, Cities, and the rest) along with the Census summary levels each group covers. Call it before you build a filter so you pass a group name the API recognizes instead of guessing.

Build target lists in your own tools

The most common use is Clay-based sourcing. Point Clay at the Accounts API and build target lists off the same public sector universe your Radar signals run on, rather than stitching together Census exports and manual research.

What It Doesn't Do

The Accounts API returns account reference data only. Radar signals, Intel documents, Research column values, and contact records are not part of this endpoint.

Next Step

See "How to search Pursuit accounts with the API" to make your first request.