Create a webhook for a seller
/sellers/{seller_id}/webhooksAuthorizationBearer token (JWT) · headerrequiredseller_idintegerrequiredapplication/jsontopicstringrequiredSupported topics: order.created, order.updated,
order.updated.closed, order.updated.shipped,
customer.created, customer.updated, customer.opted_in,
customer.opted_out, product.created,
product.updated, product.deleted.
The plural spelling (orders.created) is accepted too; either way the subscription
receives the singular one. See the Webhooks section for the topic spelling and what each
customer event means.
urlstringrequirednotify_originbooleanIf false, does not notify the request-originating host
authobjectShow propertiesHide properties
typestringnonebasicusernamestringpasswordstringWebhook created
_linksHalLinksidintegerchannel_idintegertopicstringThe topic, spelled the way this subscription receives it (see topic_style).
topic_stylestringHow the topic is spelled in the notifications this subscription receives. Subscriptions
created through v2 are singular; those created before the singular spelling existed,
or through v1, stay plural so their consumers are not affected.
singularpluralurlstringstatusstringactive — receiving deliveries normally.
failed_activation — the initial activation handshake failed.
failed — disabled automatically after 100 consecutive non-2xx delivery
responses (see error_count); can be re-enabled via
PUT /webhooks/{id}/reactivate.
disabled — the target URL returned 410 Gone; disabled immediately,
with no retry threshold. Also reactivatable via the same endpoint.
activefailed_activationfaileddisabledauthobjectnotify_originbooleanapp_idintegererror_countintegerlast_errorstringlast_error_onstring<date-time>created_onstring<date-time>updated_onstring<date-time>Token lacks the scope required to subscribe to this topic