Updates

WSC Sports notifies you when catalog content changes, so you don't have to poll the content catalog for it. Notifications are delivered as webhooks to an endpoint you register.

Principles of operation

Webhooks are event-driven messages. The platform tracks content activity and pushes a payload to your endpoint when an event occurs. The overall payload format is the same across all content types (Stories, Moments, Videos). However, the inner content object has differences according to content type.

Complete examples, organized by content type, are provided on the pages associated with this article.

To set up a webhook for WSC Sports, follow the setup instructions below and then provide your account manager with the webhook URL and credentials.

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 content catalog endpoints.