Create Link Delivery

post

https://api.seismic.com/link-delivery/v1/deliveries

Creates delivery for a DSR engagement created via the Create DSR or Create DSR
from Template APIs and returns the resolved access link URL.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Delivery registration payload. Must include an existing dsrId created by POST https://api.seismic.com/dsr/v1/dsrs. Include recipients when known so downstream engagement can be attributed to specific viewers. Based on the public controller DTO in this repository, the request body accepts only dsrId and recipients.

Request payload for creating a tracked DSR delivery.
Preconditions: - The DSR must already exist. - Use the id returned by POST https://api.seismic.com/dsr/v1/dsrs as dsrId. - The public DTO in this repository supports only dsrId and recipients.
Recipient attribution: - Include recipients to identify who received the DSR. - Recipient data powers session summary attribution, including who viewed which
content and page-level engagement where available.

Recipient email addresses can be used to notify recipients after a seller
updates DSR content.

Conditional requirement for recipients: - Required when buyer SSO is enabled in the service implementation. - Optional otherwise, but the service code expects an array and validates email
addresses for any supplied recipients.

dsrId

string

required

Existing DSR identifier to deliver. Use the id returned by POST https://api.seismic.com/dsr/v1/dsrs.

recipients

array of objects

People who receive the delivered DSR link. Provide recipients whenever possible so engagement analytics can attribute sessions to individuals and report what content/pages were viewed in DSR session summaries. In the service implementation in this repository, this field is required when buyer SSO is enabled and optional otherwise. If you do not know the recipients and SSO is disabled, send an empty array instead of null.

recipients

Responses

201Successfully created the delivery record. Returns the browser-ready linkUrl for the delivered DSR.

400Invalid request data. Common causes include invalid email addresses, missing recipients when buyer SSO is enabled, or attempting to register a duplicate delivery for the same DSR.

401Unauthorized - Missing or invalid bearer token

403Forbidden - Caller does not have permission to deliver this DSR

404Not Found - The referenced DSR does not exist

500Internal Server Error