TEN2 Media

Partner Integration Guide

DDEX Content Delivery

Send content to
TEN2 via DDEX

This guide covers everything you need to deliver audio and video releases to TEN2 Media using the DDEX Electronic Release Notification (ERN) standard, including the S3 delivery path, supported content types, and what to expect from us after delivery.

DDEX Standard

ERN 3.8

Content Types

Audio & Video

TEN2 Party ID (DPID)

PADPIDA202401120F5

Delivery Method

AWS S3

S3 Delivery

Where to upload your content

TEN2 will provision an IAM credential pair (access key + secret) scoped to your partner prefix. Use any S3-compatible client to upload your batch.

S3 Connection Details

Bucket

s3://ten2-content-deliveryProvided by TEN2 - contact us to confirm your environment endpoint.

Your prefix

<partner-code>/Your partner code is assigned by TEN2 and is case-sensitive.

Region

us-east-1

Access key

Secret key

DDEX Message

Message header requirements

Your DDEX XML must include a valid MessageHeader identifying TEN2 as the recipient.

MessageHeader - Required Values

MessageRecipient
PartyId

PADPIDA202401120F5TEN2 Media's DDEX Party Identifier (DPID).

MessageRecipient
PartyName

TEN2 Media

MessageSender
PartyId

<your DPID>Your registered DDEX Party Identifier.

MessageControlType

LiveMessageAll deliveries are processed as live. Coordinate with TEN2 before your first batch.

MessageId

<unique per message>A unique identifier for this message - used for acknowledgement correlation.

Process

How a delivery works end-to-end

Once your credentials are set up, the delivery loop is fully automated.

Prepare your batch

Create a batch folder under your partner prefix and include the DDEX XML file(s) for your release(s). The XML must conform to the ERN 3.8 standard and include the required header values outlined above. If your submission includes assets (audio/video files), they must be referenced in the XML with their expected S3 paths and uploaded to the same batch folder.

Upload your XML and related files to S3

Upload your NewRelease_*.xml file along with any referenced assets to a batch folder at s3://ten2-content-delivery/<partner-code>/<batch-folder>/. Do not upload BatchComplete.xml yet.

Signal delivery complete

Upload an empty BatchComplete.xmlfile to the same batch folder once everything else has transferred completely. This is the trigger that tells TEN2's ingest system the delivery is ready to process.

TEN2 ingests your release

Our system scans S3 on a regular schedule, detects the BatchComplete.xml signal, and queues an import job. The XML is parsed, normalized, and assets are created or updated in the TEN2 catalog. The BatchComplete.xml is removed after processing begins to prevent double-ingestion.

Receive an acknowledgement

After processing, TEN2 writes an Acknowledgement.xml file back to your batch folder. This is a standard DDEX FtpAcknowledgementMessage containing the result status.

Complete

All releases in the batch were imported successfully.

Incomplete

Some releases succeeded, some failed. Review your XML and contact TEN2.

Failed

No releases were imported. Check required fields and file accessibility.

Onboarding

Getting started

All deliveries are processed as live; there is no sandbox mode. TEN2 will coordinate a supervised first batch with you during onboarding to verify your pipeline end-to-end before you begin regular deliveries.

Contact TEN2 to receive your partner code, S3 credentials, and to schedule an onboarding call.

Send content toTEN2 via DDEX

Where to upload your content

Message header requirements

How a delivery works end-to-end

Getting started

Send content to
TEN2 via DDEX