API Updates - September 2026

Exports

This month adds new ways to deliver data with POST /api/v1/exports: more than one destination per export, signal-state audiences and single-identifier match key files.

Send One Export to Multiple Destinations

One export can now deliver the same data to up to five destinations, each on a different connection. Each destination keeps its own delivery settings, and each run is charged once however many destinations receive it. To create the export and all of its destinations in one call, pass additional_destinations to POST /api/v1/exports. To add a destination to an existing export, use POST /api/v1/exports/{id}/destinations.

Deliver an Audience's People by Signal State

Audience exports accept an optional query.signalState that delivers only the audience's people in that Predictive Signals state on the latest signals day. Accepted values are in_market, entered_market, new, rising, steady and cooling, and the export must deliver people to S3, email, Slack, HubSpot or Salesforce records, or DelivrDSP. Set it when you create the export with POST /api/v1/exports.

Match Key Exports and Household IP Targeting

A new match_key record type for S3, email and Slack destinations writes a file from an audience with exactly one identifier column: hem, uid2, maid or household_ip. You can use it to activate a Delivr audience on platforms that take match-key uploads. DelivrDSP destinations now also accept household_ip for audience exports in cumulative mode, with at least 1,000 IPv4 networks, so an audience can be targeted by household network as well as by device ID.

Identity Lookup

The lookup endpoints accept LinkedIn profile URLs and can resolve many keys in one request.

Batch Lookup

POST /api/v1/lookup/batch resolves up to 1,000 hashed emails, emails or LinkedIn profile URLs in one request, with results returned in input order. You are billed only for the records the batch returns; misses and filtered-out records are free.

LinkedIn Profile URLs

GET /api/v1/lookup accepts a linkedin_url parameter, and POST /api/v1/lookup/batch accepts linkedin_url keys. Both return the same identity record an email lookup returns, so you can enrich contacts you have no email for.

Intent

You can now match intent at the person level and filter intent audiences on topic trends.

Match Intent Across a Person's Addresses

POST /api/v1/intent/lookup and POST /api/v1/intent/batch accept an opt-in resolve_person flag. When it is set, a hem or email is first resolved to the person who holds that address, and intent is matched across every address they hold.

Intent Trend Filters

Intent audiences created with POST /api/v1/audiences can filter on intent_trend (whether a person's interest in a topic is new, rising, steady or cooling) and active_days_14d (how many of the last 14 days they were active on the topic). Filtering on either field requires tier: predictive_signals, which also adds both columns to every record and bills as Predictive Signals.

Bug Fixes

• POST /api/v1/intent/company and POST /api/v1/intent/company/batch now return every topic you name in topic_ids that the company has intent on, however many topics it has.
• S3 exports created with POST /api/v1/exports that do not set their own path_format now use the connection's path format, and exports with combine_output write the combined file under the configured prefix and path format.

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