1. Get an API key
Generate a key from your API Access dashboard. Keys look like:vp_live_...— production key, billed against your planvp_test_...— test key, same shape and validation, scoped to a sandbox dataset
2. Make your first request
Every request needs your key in theapi-key header. Here’s the simplest
possible call — checking the API’s health (no key required):
Response
3. Run your first authenticated search
Now check whetheracme-corp.com has any exposed credentials. This is the
most common starting query and requires the search:domain scope (present
on every tier).
Response
login and url are partially masked — this is the free-tier
masking policy. Upgrading to pro or ultra returns these
fields unmasked.
4. Handle pagination, errors, and rate limits
Most list endpoints are cursor-paginated — see Pagination. Every response uses the same envelope — see Response Envelope. Errors share one shape across the whole API — see Errors.Next steps
- Authentication — key formats, header styles, rotation
- Rate Limits & Tiers — what each tier allows
- Domain Intelligence — your first capability area