API Updates - October 2026

Audiences

Audiences can now be read as JSON records and built from the people who visit your website.

Audience Records

Page through an audience's rows as JSON with GET /api/v1/audiences/{id}/records, following next_cursor until a page has none. Your application can load audience data directly without downloading and parsing files. Build the audience first with GET /api/v1/audiences/{id}/download.

Website Visitor Audiences

Build an audience from the people your pixels identified: send POST /api/v1/audiences with type pixel and your source_pixel_ids. On contact and intent audiences, a WEBSITE_VISITORS condition (in or not in) can require or leave out the people in a website visitor audience from the same project. Manage these audiences with the existing endpoints, such as PUT /api/v1/audiences/{id} and POST /api/v1/audiences/{id}/refresh.

Events API

New v3 routes tell you who visited your site, not just which events happened, and break a day's web events down by field.

Website Visitors

GET /api/v3/events/{tier}/visitors returns one row per person (or per company with kind=accounts on resolution_full_profile), not one row per resolution event. Use it to answer "who visited" over a time window without removing duplicate people yourself.

Web Event Breakdowns

GET /api/v3/events/web_event/counts counts a project's website events over a window of up to 24 hours starting within the last 30 days, and you can narrow it to a single pixel. Filter with the existing filter language and group results by up to two fields. It returns counts only and is not billed.

Predictive Signals

New lookups return per-person intent trends.

People Signals Lookup and Batch

POST /api/v1/signals/people/lookup and POST /api/v1/signals/people/batch return a person's high and medium intent topics that have a trend. You can look people up by hem or email, using an API key. Usage is billed as Predictive Signals, and a dry run (dry_run: true) returns the cost without billing and without needing a payment method on file.

Dry Runs Without a Payment Method

Dry runs (dry_run: true) on POST /api/v1/contact/query work without a payment method on file. A dry run returns the cost of the request and is not billed.

Intent

Person intent lookups now answer for the whole person.

Person-Level Intent Matching

POST /api/v1/intent/lookup and POST /api/v1/intent/batch now resolve an email, hem or linkedin_url to the person who holds it. They return that person's topics across all of their addresses, so an address with no intent of its own can still match. Matched results include a person_id you can send back to read the same person directly, and POST /api/v1/intent/people returns one row per person.

Email Identity

Get email tokens through the API, and record email opens with the pixel.

Email Tokens API

POST /api/v1/email-tokens returns a dlvr_et token for each email address you send for a project_id, using your organization API key. If your code syncs contacts into an email platform, it can now get tokens without the dashboard's CSV upload.

Email Open Tracking

GET /pixel/core/api/send-event/get accepts event_type=email_open and responds with a 1x1 image. Put it in your emails with the recipient's dlvr_et merged in to record which recipient opened them.

Integrations and Exports

You can now deliver exports to your own HTTPS endpoint.

Webhook Connections

Create a Webhook integration with POST /api/v1/integrations by giving a name and an HTTPS URL. Delivr generates the signing secret and returns it only in that response; rotate it with POST /api/v1/integrations/{id}/webhook-secret. Use the connection as a destination on POST /api/v1/exports to receive Predictive Signals exports, or a pixel's resolved website visitors every 5 minutes on the continuous schedule.

Campaigns

Campaign reads now report more delivery detail, and campaign writes support more targeting options.

Campaign Insights

GET /api/v1/campaigns/{id}/insights is now open to customers. Use it to see why a campaign is or isn't delivering.

Bids, Win Rate and Viewability

GET /api/v1/campaigns/{id}/performance now includes bids, win rate and viewability, both per day and in the summary.

Operating System and Browser Targeting

POST /api/v1/campaigns and PUT /api/v1/campaigns/{id} accept operating system and browser targeting alongside device and connection types. For example, you can restrict a campaign to Chrome only.

Bug Fixes

• Launching a campaign whose creatives are all still drafts now activates those creatives, so the campaign can serve.
• Audiences built from a list can now be downloaded with GET /api/v1/audiences/{id}/download and resumed with POST /api/v1/audiences/{id}/resume.
• Short job-title keywords in persona audiences (for example "cto" or "coo") now match only as whole words, so "cto" no longer matches inside titles like "Director".

For full endpoint details, parameters, and examples, see our developer documentation.