What is rest api?
A REST API is a web interface that lets applications request and exchange data over standard HTTP methods, returning structured JSON — the programmatic way to search, reveal, look up, and enrich contacts from a data platform.
A REST API is the standard contract between your software and a service. Your application makes an HTTP request to a documented endpoint, optionally with parameters, and gets back structured JSON it can parse and act on. Because it speaks plain HTTP and JSON, it works from any language and slots into any stack without special libraries.
For a contact platform, the REST API mirrors what the app does. There are endpoints to search the dataset with the same filters you'd use in the UI, to reveal a contact's verified details, to look up or enrich a specific record, and to check your usage. Each returns predictable JSON, typed errors that tell you what went wrong, and rate-limit headers so your integration can pace itself.
The design goal is that an integration behaves like a good teammate: predictable, well-documented, and honest about limits. Clear errors beat silent failures; explicit rate-limit headers beat guessing; consistent response shapes mean you write the parsing once. Those qualities are what let you build on the API with confidence rather than defensive guesswork.
A REST API pairs naturally with an MCP server for AI-native workflows. The REST endpoints serve traditional code; the MCP server exposes the same capabilities as tools an AI agent can call directly. Same data, same credits, same verification — two front doors onto one platform.
Frequently asked questions
What can the REST API do?
It mirrors the app: search contacts with full filters, reveal verified details, look up or enrich specific records, and check usage. Responses are JSON with typed errors and rate-limit headers, and spend draws from the same never-expiring credits.
What languages can call the REST API?
Any language that can make an HTTP request and parse JSON — which is all of them. A REST API speaks standard HTTP, so no special SDK is required, though typed errors and clear docs make integration quick in any stack.