Changelog
Back to All
Added

API Updates - September 2026

about 1 month ago

Exports

POST /api/v1/exports can now deliver to several destinations at once, deliver an audience by signal state, write single-identifier match key files and send household networks to DelivrDSP.

Send One Export to Multiple Destinations

One export can deliver the same data to up to five destinations, each on a different connection and with its own delivery settings. Each run is billed once, however many destinations receive it.

To create the export and all of its destinations in one call, pass additional_destinations:

POST /api/v1/exports

Parameters:

  • additional_destinations (array) - Extra destinations that receive the same data as the export's primary destination. An export can have up to five destinations in total.

To add a destination to an export that already exists:

POST /api/v1/exports/{id}/destinations

Parameters:

  • id (string, path) - The export ID.

To change the settings of a destination you added (change the original destination with PUT /api/v1/exports/{id}):

PUT /api/v1/exports/{id}/destinations/{destinationId}

Parameters:

  • id (string, path) - The export ID.
  • destinationId (string, path) - The added destination's ID.

Deliver an Audience's People by Signal State

Audience exports accept an optional query.signalState. When it is set, the export delivers only the audience's people in that Predictive Signals state on the latest signals day, billed at the Predictive Signals rate.

POST /api/v1/exports

Parameters:

  • query.signalState (string, optional) - One of in_market, entered_market, new, rising, steady or cooling.

Requirements:

  • The export must deliver people to S3, email, Slack, HubSpot or Salesforce records, or DelivrDSP.

Match Key Exports

The new match_key record type writes a file from an audience with exactly one identifier column. Use it to activate a Delivr audience on platforms that accept match-key uploads.

POST /api/v1/exports

Parameters:

  • record_type: match_key - Available on S3, email and Slack destinations.
  • match_key (string) - Exactly one of hem, uid2, maid or household_ip.

Household IP for DelivrDSP

DelivrDSP destinations now accept the household_ip identifier for audience exports. This lets an audience reach TVs by household network as well as by device ID.

Requirements:

  • The export must run in cumulative mode.
  • The audience must resolve to at least 1,000 IPv4 household networks, or the run fails.

Identity Lookup

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

Batch Lookup

POST /api/v1/lookup/batch

Resolves up to 1,000 keys in one request. Keys can be hashed emails, emails or LinkedIn profile URLs (linkedin_url).

Response:

  • Results come back in the same order as the input.

Billing:

  • You are billed only for records the batch returns. Misses and filtered-out records are free.

LinkedIn Profile URLs

GET /api/v1/lookup

Parameters:

  • linkedin_url (string, query) - A LinkedIn profile URL.

Response:

  • The same identity record an email lookup returns. You can use it to enrich contacts you have no email for.

POST /api/v1/lookup/batch also accepts linkedin_url keys, as described above.

Example:

curl -G https://api.delivr.ai/api/v1/lookup \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "X-Api-Secret: YOUR_API_SECRET" \
  --data-urlencode "linkedin_url=https://www.linkedin.com/in/example"

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
POST /api/v1/intent/batch

Parameters:

  • resolve_person (boolean, optional) - Off by default. 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 that person holds.

Intent Trend Filters

Intent audiences created with POST /api/v1/audiences can now filter on two new fields.

POST /api/v1/audiences

Parameters:

  • intent_trend - Whether a person's interest in a topic is new, rising, steady or cooling.
  • active_days_14d - How many of the last 14 days the person was active on the topic.
  • tier (string) - Must be predictive_signals to filter on either field.

Response:

  • With tier: predictive_signals, every record includes both the intent_trend and active_days_14d columns.

Billing:

  • These audiences bill as Predictive Signals.

Bug Fixes

  • POST /api/v1/intent/company and POST /api/v1/intent/company/batch now return every topic in topic_ids that the company has intent on, no matter how many topics the company 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.