Write Restrictions

GET /restrictions returns, per Property and date (up to 100 Properties and 366 days per call), the current values and unwritable_fields: the fields a batch will refuse on that date, and why. Skip them instead of discovering refusals afterwards.

With "dry_run": true, ZenHost answers 200 with what would change on each Property (current and new value per date and field, and the refused fields), without storing or sending anything. Test your script against the real calendar this way. A dry run still counts against the submission limit of 10 per 60 seconds.

Without dry_run, ZenHost answers 202 with the batch id. Send an Idempotency-Key header (one per logical run): replaying the same key on the same App Connection within 24 hours returns the batch it created instead of a second one, so a retry after a timeout is safe. The same key with a different body answers idempotency_key_reused.

Limits: up to 20,000 entries over 100 Properties and 200,000 date × field changes per batch (one batch per page of GET /properties covers any account); dates from today to today + 730 days, both read in the time zone of each Property. A malformed body, a date outside that range or a Property outside your Connection Scope rejects the whole batch with 422; nothing is stored.

Read GET /restriction-batches/{id}, or wait for the restriction_batch.completed App Event instead of polling. The batch moves from queued and processing to a final status: completed, partially_failed, failed or cancelled. For each Property, the report counts the changes applied, unchanged, superseded, refused, failed and cancelled, and lists refused fields and failures as runs of dates. Reports are kept 30 days.

• Properties succeed or fail on their own: a refused Property never blocks the others, and nothing is rolled back.
• Batches apply in submission order: on the same date and field, the latest batch wins and the older change, if not sent yet, is superseded (not a failure).
• A value equal to the current one is unchanged and is not sent again: pushing an identical calendar every day costs nothing on the Sales Channels.
• A field the host froze after you submitted is still refused at send time with manual_override.
• If the owner revokes the connection (or you revoke your last refresh token), ZenHost suspends your App, or the account is no longer allowed on your Private App, changes not sent yet are cancelled at once and are never replayed, even if the App is reactivated. The same happens to the changes of a Property the owner removes from your Property Access (or leaves out when connecting again), and to all of them once your App no longer holds restrictions.write: the Connection Scope is checked again when sending. A change already on its way to the Sales Channels completes.