Catalog API Webhook updates
Get notified when Catalog content changes, so you don't have to poll the Catalog API. Notifications are delivered as webhooks to an endpoint you register.
Catalog webhooks use the V2 payload in this section. Action is Create, Update, or Delete. On Delete, the payload carries the content ID and no content body.
The V1 Stories feeds pages in this section are a different, older Feeds API. They are not the Catalog pull API and not this webhook.
Setup and endpoint for WSC Sports
- Provide a publicly exposed endpoint URL that WSC Sports can call.
- The endpoint must start with
https://. - Endpoint should support any of the following static authentication mechanisms:
- Basic: Provide a username and password. The credentials are sent in the Authorization header
- ApiKey: Provide an API key value. The key is sent using the x-api-key header.
- Bearer: Provide a token value. The token is sent in the Authorization header.
- Oauth2: Currently not supported.
Refresh and changes
Webhooks send data about content that is published or changes after the webhook is set up. As such, you must also import the existing content catalog using the Catalog API endpoints.
Updated about 1 month ago
Did this page help you?
