Retrieve an access schedule
/products/{product_id}/access-schedules/{access_schedule_id}Retrieves an access schedule by its public ID, including the deliveries that use it (deliveries[]).
The response includes an ETag representing the current revision of the access schedule. Send this value in the If-Match header when updating the access schedule or its release rules to avoid overwriting a newer version.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/products/string/access-schedules/string"{ "data": { "created_at": "2019-08-24T14:15:22Z", "default": true, "deleted": true, "deliveries": [ { "id": "string" } ], "deliveries_count": 0, "id": "string", "name": "string", "object": "access_schedule", "product_id": "string", "revision": "string", "rules_count": 0, "tag_id": "string", "updated_at": "2019-08-24T14:15:22Z" }}Create an access schedule POST
Creates an access schedule for the product, identified by the supplied tag. Each tag and product pair has at most one access schedule. If one already exists for the pair, the existing schedule is returned with `200 OK` and no new schedule is created. Access schedules cannot be created for replicated products; these requests return the `replica_readonly` error code.
Update an access schedule PATCH
Renames or restores an access schedule. The access schedule takes its name from its tag, so changing `name` renames the tag everywhere it is used and also requires the `tags.update` permission. Setting `deleted` to `false` restores an access schedule from the trash. Replicated access schedules are read-only and return the `replica_readonly` error code. Send the current `ETag` value in the `If-Match` header to avoid overwriting a newer version.