SetAllWebhookSettingsRequest

Fields

• newUrlstring

  The new signed destination to register.

  Omitted -> the stored newUrl is left alone. A url -> registered, and at least one entry in newUrlEvents must accompany it in the SAME call. Explicit null -> the destination is cleared, which is refused with 400 when it would leave the organization with no webhook destination at all (no legacyUrl on file). Prefer newUrlEnabled: false to stop delivery: pausing keeps the registration, clearing throws it away.

• newUrlEventsstring[]

  Which events newUrl receives.

  Omitted -> the stored subscription list is left alone. PRESENT -> it REPLACES the stored list wholesale, so [] genuinely means "no events" and this is not an append. Must contain at least one entry whenever newUrl is sent as a url.

  Possible values: [order.created, order.status.updated, order.rejected, order.cancelled, order.delivery.updated, store.status.changed, report.completed, menu.publication.completed]
• newUrlEnabledboolean

  Pause switch for newUrl only. Omitted -> left at its stored value.

• legacyUrlEnabledboolean

  Pause switch for legacyUrl only (ONE-2877). Unlike legacyUrl itself — which has no field on this request at all and is rejected with 400 if sent — this one IS settable: it is the only way a partner can turn the legacy feed off themselves. false stops legacy delivery immediately; setting it back to true resumes it.

  OMITTING IT LEAVES LEGACY DELIVERY EXACTLY AS IT IS (ONE-2903). It used to be read as false, which meant registering a newUrl without naming this field switched a partner's live legacy order feed off, with a 200 and no warning. That is fixed; you never need to restate this field to keep legacy running.