ContractRadar Now Has an API — In Beta, for the Few of You Who Want It

Most ContractRadar users never need this post — you save a search, switch on alerts, and the matches come to you. This one is for the smaller group who want to pull contract search into something they’re building themselves: a script, an internal tool, a Zapier-style pipeline of your own. If that’s not you, nothing about how ContractRadar works day to day has changed.

For that group: ContractRadar now has an API. It’s one endpoint, it’s in beta, and it’s available on Pro.

What it does

The API is the same contract search the web app runs, callable directly — GET /api/v1/posts. Send a query, a state, a date range, a tag, whatever combination of filters you’d normally set on the search page, and get contracts back as JSON instead of a rendered page. Same semantic matching, same coverage, same data — just a request you can call from your own code instead of a browser.

That’s the whole feature. It’s read-only: it searches, it doesn’t write anything back, and it doesn’t do anything the web app can’t already do for you by hand.

Beta means beta

This is a first cut, not a finished product. There’s no version number and no stability promise yet — the response shape can change without notice while we learn what people actually build with it. If you wire it into something, expect to keep an eye on it, and tell us what you’re building. That feedback is what decides whether this becomes a stable, versioned API.

Getting a token

If you’re on Pro, generate a token from your profile under API Access. It’s shown once, so copy it somewhere safe — treat it like a password, not something to paste into a browser or commit to a public repo. Full details, request parameters, and the response shape are in the API reference.

Not on this list

To be clear about scope: there’s no write access, no webhooks, and no separate scoring endpoint — just the one search call described above. If any of that changes, it’ll get its own announcement.

Try it

If contract search belongs in something you’re already running — a script, an internal dashboard, a pipeline into another tool — generate a token from your profile and start with the API reference. Everyone else: nothing to do here — your saved searches and daily alerts work exactly as they did yesterday.