Build on Delivr

Use this page if you put Delivr intent or identity lookup inside your own product. It lists the free evaluation calls and your obligations in order. You need an organization API key. You do not need a project or a pixel.

1. Try the request shapes with a test key

Create a key with the Test environment. A test key returns mock data from the sandbox and is never billed. See Create your API key in the dashboard.

To use a typed client instead of raw HTTP, see SDKs and MCP.

2. Judge real data for free

Create a Live key. Previews return up to 25 real records and bill nothing. A dry_run request returns the billable count and bills nothing. Neither one needs a payment method.

3. Make the call

Pick the endpoint from the data you start with. See Which API Should I Use?.

Quickstart: enrich emails with intent
Quickstart: find people on a topic
Identity lookup: one key or a batch of up to 1,000 keys
Rate limits and what gets billed

4. Track usage and separate your customers

Who am I validates a key and bills nothing.
The billing usage API reports your usage. Usage by meter splits it by meter.
A project-scoped API key reaches one project. Issue one key per customer to attribute usage to that customer.
A project budget caps the spend of one project.

5. Meet your embedded-use obligations

These apply if your agreement grants Data Rights Tier 2 (Embedded Use).

Storing and reusing records: re-query a record before it goes into new output once 90 days have passed since Delivr last returned it.
Suppression notices: process each notice, and forward it to every End Customer who received Delivr data.
Quarterly reports: send Delivr a report for each calendar quarter.

6. Pass your security review

Security and Compliance links the Trust Center, the subprocessor list and the Data Processing Addendum.