https://api.datalayer.so. Run the examples from
your terminal or backend, with DATALAYER_API_KEY supplied through your private
environment or secret manager. Never embed it in frontend code or commit it to Git.
Data requests share a limit of 60 per minute per account. Request bodies are
limited to 16 KiB. Pass dry_run: true for a maximum credit estimate with no
lookup, and max_credits to cap a real call. See
credits, receipts and safe retries and
errors.
1. Check your key
This authentication check does not look up data or use credits.2. Search for a company
company_id from
the returned results. On the published plan for new signups, a search with results uses 1 credit. An empty search does not. A search still requires an active
allowance and counts toward the account request limit.
3. Retrieve the selected company
SetCOMPANY_ID to the returned ID. Set REQUEST_ID to a unique identifier for this
lookup, such as a UUID. Keep that identifier for retries of the same request.
meta.credits_used and
meta.billing_status in the response. Eligible repeats and idempotent replays use
zero additional credits. A timeout alone does not prove zero usage; retry with
the same key and unchanged input. See usage and retries.
Next steps
- Read the allowance with
GET /v1/account/details. It uses no credits. - Find people using a query or company name.
- Get a person, optionally including work email.
- Read authentication and errors before integrating.
Public names and earlier names
Call the public names. Earlier names still run with the same behavior and billing, and a renamed tool is hidden from the connector’s tool list. Earlier REST paths keep working beside the current ones. MCP calls may still use an earlier path internally. Prices are unchanged.
Plain-language use of each tool is on what you can do. The pages in
this API reference use the current paths and public names.