Skip to main content
The Find.ly API gives your scripts and servers the same searches as the Find.ly dashboard: leak records, selectors for a domain and raw files. It is a small JSON-over-HTTPS API with two endpoints.
API access comes with the Professional (500 requests a day) and Enterprise (1,500 requests a day) plans. See pricing.

​
Base URL

HTTPS only. Every response is sent with Cache-Control: no-store.

​
Endpoints

{module} is one of intelligence-search, phonebook, identity-portal, system-id or storage-id. See Modules and inputs.

​
How it works

  • One account, one quota. A key acts as your account. Searches made through the API and in the dashboard share the same daily quota and the same per-account limits.
  • Every response tells you what it cost. JSON responses carry billed and a usage object; JSON and text responses carry X-Request-Billed, and X-Quota-* headers whenever the quota is known.
  • Errors are free. Invalid input, refused calls and service failures never use a request. See Billing and quotas.
  • Server-side only. The API sends no CORS headers: browsers cannot read its responses. Call it from a server, a script or a terminal, never from a web page.
  • Nothing is stored. Search results are sent back to you and not kept, so there is no server-side pagination: you get the whole list (up to 5,000 items) at once. See Pagination.

Quickstart

Your first call in a minute, with curl.

Authentication

Get your key and send it the right way.

Modules and inputs

Request bodies and responses for each module.

Errors

Every error code, its status and what to do.