Developers
Deliveries12

List delivery release schedules

GET/sales/deliveries/{delivery_id}/rules

Returns the release schedules applied by the delivery, with one entry for each product it grants access to.

Products without a release schedule are included with a null schedule_id, meaning their content is released without a schedule.

Authorization

AuthorizationBearer <token>

Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.

In: header

Path Parameters

delivery_id*string

Public ID of the delivery, prefixed with dlv_.

Header Parameters

X-Client-Request-Id?string

Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.

Lengthlength <= 64

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/sales/deliveries/string/rules"
{  "data": {    "entries": [      {        "links": {          "schedule": "string"        },        "product_id": "string",        "schedule_id": "string"      }    ],    "object": "delivery_rules"  }}

Replace delivery products PUT

Replaces the delivery's entire product set with the supplied entries. Existing enrollments are not changed; the new set applies to subsequent sales. Every referenced product must be accessible with the current credentials. Replicated deliveries are read-only; replacing their products returns `403` with the `replica_readonly` error code. To avoid overwriting a newer version, send the delivery's current `ETag` in the `If-Match` header.

Replace delivery release schedules PUT

Replaces the release schedules applied by the delivery. Changes apply only to new enrollments. Existing enrollments keep the release schedule assigned when they were granted.