Real-time Liveblog Updates with Webhooks and Liveblogs API

Summary This article explains how to use webhooks and the Liveblogs API to surface real-time liveblog content (including match and non-match events) in an external news feed, and describes a recommended configuration pattern for notifying and fetching liveblog updates.

Key concepts

• Liveblogs for matches: Liveblogs that are tied to matches can be fetched directly because the liveblog ID is known. Use the Content API endpoint /liveblogs/{liveblog_id} to retrieve the liveblog content for a specific match.
• Liveblogs for other events: For non-match breaking-news liveblogs (transfers, gala coverage, etc.) external systems need to be notified when a new liveblog is created so the feed can show the new content without polling.

Recommended configuration and workflow

1. Subscribe to liveblog webhook events

   • Configure your webhook subscription to receive events for the LIVEBLOG entity type. When a liveblog (match or non-match) is created or updated, your webhook will receive an event notifying your system.

2. Handle incoming LIVEBLOG webhook events

   • When you receive a LIVEBLOG webhook event, extract the liveblog identifier included in the event payload.
   • For immediate display in your feed, use that identifier to fetch the full liveblog content from the Liveblogs API.

3. Fetch liveblog content

   • For liveblogs tied to matches, call the Liveblogs API endpoint:
     • GET /liveblogs/{liveblog_id}
   • Use the API response to render or update the liveblog in your front-end news feed or application.

4. Use-case alignment

   • Surface breaking-news liveblogs (transfers, gala coverage, editorial liveblogs) in real time without requiring constant polling or manual discovery.
   • For match coverage, continue to use the match-linked liveblog IDs and the Liveblogs API to retrieve match event updates.

Prioritization guidance

• Assign an integration priority reflecting how quickly your downstream systems must show new liveblog entries. A medium priority is appropriate for real-time news feeds that must keep users updated without excessive urgency.

Deployment status note

• Support for delivering LIVEBLOG entity webhook events has been implemented and is available for use. Set up webhook subscriptions to receive those liveblog events and combine them with calls to the Liveblogs API to fetch content.

Conclusion Subscribe to LIVEBLOG webhook events so your system is notified when new liveblogs are created (especially for non-match breaking news). On receiving a webhook, fetch the liveblog using /liveblogs/{liveblog_id} to display up-to-date liveblog content in your feed. This combination avoids polling and ensures timely updates for both match and non-match liveblog coverage.