Systems operational live
  • Data Ingest records ingested 24h
  • Metadata Production assets enriched 24h
  • Media & Image Hub images processed 24h
  • Content Delivery API requests served 24h
  • Platform availability uptime 30d

Representative platform activity · updated continuously

850+ clients 7,140 channels 2.4M sport events

Platform · Module

Content Delivery deliver through the channel you prefer

Content Delivery is the outbound layer of the MP Platform. This is where finished metadata and visual assets leave the platform and arrive with you: in the format you use, through the channel you prefer, with full visibility into exactly what was sent.

The flow

What goes in, what comes out

IN

complete, validated records and assets from Metadata Production and the Media & Image Hub.

OUT

delivery packages built to your specification, in your chosen format, sent through your chosen channel, and verifiable after the fact.

Channels

Three ways to receive data

Every product ships through the same three client-facing channels:

  • API: a real-time interface to pull exactly the data you need, when you need it
  • Data Feeds: scheduled exports delivered for you to download
  • Client Portal: a self-service view where your team browses exactly the data defined in your profile

Behind the API sits a REST interface with an OpenAPI/Swagger sandbox and SDK generation, so your developers can explore and integrate without a lengthy onboarding. Rate limits, versioning and deprecation are managed so integrations stay stable as the platform evolves.

Formats

In the format you already use

Output is built to your specification and serialised to the standard you work with, so it drops into your systems without re-engineering:

  • JSON and XML (and zipped variants)
  • TV-Anytime / TVA (XSD-validated, multiple versions)
  • XMLTV, ADI
  • CSV and Excel
  • MP-Format (Media Press proprietary)
  • your own customer-native format, mapped for you

Over 500 customised delivery configurations are already in production, so a non-standard requirement is routine rather than a special case. Device-specific deep links (iOS, Android, TV, HbbTV) are delivered with fallback logic, so a viewer is taken straight to the right place to watch.

Transport

Through your preferred channel

Delivery is not limited to one transport. Packages can be sent via SFTP, SCP or FTP, to AWS S3, Azure Blob Storage or SharePoint, pushed to a REST endpoint or SOAP, sent by email, or streamed to a customer Kafka topic, whatever fits your infrastructure.

Update modes

Only the changes that matter

You choose how updates arrive:

  • Full export: the complete dataset or a full EPG/VOD window
  • Delta export: only the records whose output actually changed
  • Block delta: a larger block refreshed when one object in it changes (for example, a full EPG day)
  • Near-real-time push: changes propagated to your endpoint or storage as they happen
  • Notification and pull: we notify you, you pull when ready

A change is sent only when it affects your customer-facing output, not for every internal edit, so downstream systems are not flooded with updates that change nothing.

Access

Secure access, by role

Access is protected with single sign-on and role-based permissions, so each person on your team sees only what they should, including separate views per operating company in multi-country deployments.

Verification

You can verify every delivery

Content Delivery keeps an immutable record of every outbound package, matching exactly what you received. You and your technical team can:

  • inspect and search past deliveries by title, ID, date or batch
  • confirm what was sent, when, and to whom
  • track delivery volumes, timeliness and any errors

Nothing about a delivery is a black box: every package can be inspected and verified.

Cross-links

Products that live here

Get started

See the Content Delivery in action

Book a demo to see Content Delivery configured for your systems.