Back to Company Profile
Partner Technical Reference

Catalogue Delivery Format & DDEX / API Capabilities

DDEX ERN 4.1.1 catalogue delivery via authenticated HTTPS webhook and SFTP

FlipDistro supports DDEX ERN 4.1.1 catalogue delivery through an authenticated HTTPS webhook and SFTP-based delivery infrastructure. Delivery packages include the DDEX ERN XML, master audio, artwork, manifest, and SHA-256 checksums. Packages are validated prior to delivery and delivery status is tracked within the FlipDistro platform.

Version: 2.0Date: 2026-08-23Confidential - Partner Use

Integration Capability

Methods We Can Work With

FlipDistro delivers catalogue packages using DDEX ERN 4.1.1 over an authenticated HTTPS webhook, with SFTP-based delivery for large file transfers. Each delivery package contains the ERN XML, master audio, artwork, a JSON manifest, and SHA-256 checksums — all validated before delivery is attempted. Below are the delivery methods currently in production.

DDEX ERN 4.1.1

Live

FlipDistro generates and delivers Electronic Release Notification messages conforming to DDEX ERN 4.1.1. Delivery packages include the ERN XML, master audio, artwork, manifest, and SHA-256 checksums — all validated prior to delivery.

  • ERN 4.1.1 with CommonReleaseTypes/14/Audio release profile
  • Packages include ERN XML, WAV audio, artwork, manifest.json, checksums.json
  • SHA-256 checksums computed from actual binary asset content
  • WAV duration parsed from file headers and included in ERN metadata
  • Packages validated and verified before delivery is attempted

Authenticated HTTPS Webhook

Live

Delivery packages are pushed to your endpoint via an authenticated HTTPS webhook. Each push is signed with a shared secret header for verification, and delivery status is tracked within the FlipDistro platform.

  • HTTPS POST with base64-encoded package payload
  • x-webhook-secret header for shared-secret authentication
  • Delivery status tracked: pending, assembling, ready, delivered, failed
  • Automatic retry on transient failures with error logging
  • Partner webhook URL configurable per delivery batch

SFTP-Based Delivery

Live

For large file transfers and back-catalogue migrations, FlipDistro delivers structured packages to your SFTP server using SFTP, with your folder naming conventions and manifest format.

  • SFTP delivery to partner-configured host, port, and credentials
  • ISRC-based audio naming, UPC-based artwork and package naming
  • SHA-256 checksums per file for integrity verification
  • Suitable for large back-catalogue migrations and large binary assets
  • Scheduled or on-demand delivery batches

API Integration

Working With Your REST API

Delivery packages are pushed to your endpoint via an authenticated HTTPS webhook. FlipDistro assembles the package (ERN XML, audio, artwork, manifest, checksums), validates all assets, and pushes the complete package as a base64-encoded JSON payload with a shared-secret authentication header. Below are the delivery operations and status callbacks supported.

POSTPOST /webhookPush a complete delivery package (ERN XML + audio + artwork + manifest + checksums) as a base64-encoded JSON payload.
HEADERx-webhook-secretShared-secret authentication header included on every webhook push for request verification.
POSTPOST /sftpSFTP delivery of structured package files to partner-configured host, port, and directory.
GETGET /batches/{id}/statusRetrieve delivery batch status: pending, assembling, ready, delivered, or failed.
POSTPOST /batches/{id}/retryRetry a failed delivery batch — re-assembles and re-pushes the package.
GETGET /batchesList delivery batches with status filtering and pagination.
POSTPOST /ackPartner callback endpoint for ERN acknowledgement and validation feedback.
POSTPOST /status-callbackPartner async callback to report delivery confirmation or errors after ingestion.

Authentication & Delivery Tracking

Every webhook push includes an x-webhook-secret header with a shared secret for request verification. All communication is over TLS-encrypted HTTPS. Delivery status is tracked within the FlipDistro platform through the full lifecycle: pending → assembling → ready → delivered (or failed), with error messages logged for any failed delivery.

DDEX Compatibility

Working With Your DDEX Pipeline

FlipDistro generates DDEX ERN 4.1.1 messages with the CommonReleaseTypes/14/Audio release profile. Each package includes the full ERN XML (MessageHeader, ResourceList with SoundRecordings and Images, ReleaseList, and DealList), along with the actual master audio and artwork binaries. WAV durations are parsed from file headers and included as Duration elements in the ERN. SHA-256 checksums are computed for every asset and included in checksums.json for integrity verification on receipt.

Package Contents We Deliver

  • ERN 4.1.1 XML — MessageHeader, ResourceList, ReleaseList, DealList
  • Master audio — WAV file with ISRC-based naming (e.g. NG-FD1-26-80606.wav)
  • Artwork — FrontCoverImage JPEG with UPC-based naming
  • manifest.json — release metadata, track list, asset references
  • checksums.json — SHA-256 hash per file for integrity verification

Validation & Status Tracking

  • Package validated before delivery — all assets downloaded and checksums verified
  • WAV duration parsed from binary headers and included in ERN metadata
  • Delivery status lifecycle: pending → assembling → ready → delivered
  • Failed deliveries logged with error message and batch retained for retry
  • Partner ack/callback endpoint for ERN acknowledgement and validation feedback

Metadata

Delivered Metadata Schema

FlipDistro captures comprehensive metadata for each release. Our schema maps cleanly to DDEX DSR (Digital Release/Recording) message fields and can be adapted to your platform\'s JSON schema for API-based delivery. Whatever fields your pipeline requires, we can populate and deliver them.

Core Release

  • Release title
  • Release type (single / EP / album)
  • Primary artist
  • Featured artists
  • Release date
  • Original release date
  • UPC / EAN
  • Catalog number
  • Genre & sub-genre
  • Language code (ISO 639-1)
  • Explicit content flag

Track-Level

  • Track title
  • Track number / sequence
  • ISRC
  • Duration
  • Audio file reference
  • Preview clip offset
  • Composition title (if differs)
  • P-line & C-line

Rights & Clearance

  • Territory rights list (ISO 3166-1 alpha-2)
  • Rights type (exclusive / non-exclusive)
  • Rightsholder / licensor name
  • Rights validity start/end dates
  • Rights clearance status
  • Mechanical & performance rights info

Contributors

  • Display artist credits
  • Primary contributor role
  • Composer
  • Lyricist
  • Producer
  • Publisher
  • Record label
  • Copyright owner

Assets

  • Audio (WAV / FLAC master)
  • Artwork (3000x3000px JPEG/PNG)
  • Thumbnail variants
  • Audio ISRC linkage

Assets

Asset Specifications

Audio MasterWAV (16-bit / 24-bit, 44.1 kHz) or FLAC. Lossless only. No upsampling. Duration parsed from WAV headers.
Artwork3000 x 3000 px (min 1400 x 1400), RGB, JPEG or PNG, max 25MB.
ERN XMLDDEX ERN 4.1.1, CommonReleaseTypes/14/Audio profile. Named {UPC}_ern.xml.
ManifestJSON manifest with release metadata, track list, asset references, and file list.
File NamingISRC-based naming for audio (e.g. NG-FD1-26-80606.wav); UPC-based for ERN XML and artwork.
ChecksumSHA-256 checksum computed from actual binary content, provided per file in checksums.json.

Workflow

End-to-End Delivery Process

1

Release Metadata Prepared

FlipDistro compiles release and track metadata (title, ISRC, UPC, artist, genre, territory rights, deal terms) from the catalogue into the DDEX ERN 4.1.1 schema.

2

Assets Downloaded & Validated

Master audio (WAV) and artwork are downloaded from FlipDistro storage. WAV duration is parsed from binary headers. SHA-256 checksums are computed from actual file content.

3

ERN XML & Manifest Generated

The DDEX ERN 4.1.1 XML is generated with MessageHeader, ResourceList (SoundRecordings + Images), ReleaseList, and DealList. A JSON manifest and checksums.json are assembled alongside.

4

Package Assembled & Verified

All files (ERN XML, audio, artwork, manifest, checksums) are bundled into a single delivery package. The package is validated — all assets present, checksums verified — before delivery is attempted.

5

Delivery via HTTPS Webhook / SFTP

The complete package is pushed to the partner endpoint via an authenticated HTTPS webhook (with x-webhook-secret header) or delivered via SFTP. Delivery status transitions to "delivered" on success.

6

Status Tracked & Acknowledged

Delivery status is tracked within FlipDistro (pending → assembling → ready → delivered / failed). Partner ack callbacks confirm ingestion. Failed batches are retained with error logs for retry.

Onboarding

Integrating With Your Platform

Integrating with a new partner is straightforward — provide a webhook URL and shared secret, or SFTP credentials, and FlipDistro handles the rest. The process below outlines how we go from credential exchange to live catalogue delivery.

  1. 1Partner provides their webhook URL and shared secret, or SFTP credentials (host, port, user, password).
  2. 2FlipDistro configures the delivery channel — HTTPS webhook with x-webhook-secret auth, or SFTP connection.
  3. 3A test release is selected and a delivery batch is assembled (ERN XML + audio + artwork + manifest + checksums).
  4. 4The package is validated — all assets downloaded, WAV duration parsed, SHA-256 checksums verified.
  5. 5The package is pushed to the partner endpoint via HTTPS webhook or SFTP.
  6. 6Partner confirms receipt and processes the ERN — returns ack or validation feedback.
  7. 7On partner sign-off, full catalogue delivery begins — new releases pushed incrementally with status tracking.

Ready to Integrate?

Contact our partnerships team to set up DDEX ERN 4.1.1 delivery to your platform via HTTPS webhook or SFTP.

Commercial Terms