Skip to main content

reactivateWebhookSubscription

Re-activates a subscription that was disabled automatically. The destination has to consent in a fresh handshake, and an escalating cooldown after the automatic disable has to have elapsed — while it is running the mutation fails with CONFLICT and a reactivationBlockedUntil error extension.

Required scopes​

The token needs the webhook_subscriptions:write access scope.

reactivateWebhookSubscription(
  id: ID!
): WebhookSubscription!

Arguments​

reactivateWebhookSubscription.id ● ID! non-null scalar​

ID of the subscription to re-activate.

Type​

WebhookSubscription object​

A request to be notified about a topic at a destination. Notifications carry only the ids of the affected entities and a timestamp; fetch the current state through the API. Subscriptions belong to the API token that created them: a token only sees and manages its own.

Delivery itself runs outside the shop, which is why every field from active through lastErrorMessage is a mirror of what the delivery service reports and is refreshed whenever the shop talks to it. A quiet shop's mirror can be up to a minute behind. Deliveries only start once the destination has consented, so a freshly created subscription reads consentState: Pending until then.