Bulk Upload and Large-Catalog Migration

Updated July 2026.

To migrate or upload a large catalog, use LabelGrid’s bulk tools: API integration for automated, custom workflows, or DDEX import for industry-standard feeds and distributor-scale migrations. Both are available on plans with API access enabled. Reuse your existing ISRCs and UPCs with matching metadata so streams and playlists are preserved. This guide covers both methods and how to move a distributor-scale catalog safely.

For step-by-step migration from another distributor at any scale, see Transferring Your Catalog.

Bulk Upload Methods

Available Options

Method	Best For	Plan Required
API integration	Automated workflows, custom integrations	Plans with API access enabled
DDEX import	Industry-standard feeds, major label workflows	Enterprise / API plans (contact support)

Note

Bulk upload methods are available on plans with API access enabled. If your plan does not include API access, you can create releases individually through the LabelGrid dashboard or contact support to discuss enabling API access.

---

API Integration

Overview

The LabelGrid API allows you to programmatically create and manage releases, enabling fully automated workflows for large catalogs.

What You Can Do

• Create releases programmatically
• Upload audio files via API
• Manage metadata in bulk
• Automate distribution workflows
• Integrate with your existing systems

Getting Started

1. Enable API access on your plan — contact support if it is not already enabled
2. Generate API credentials in your account settings
3. Review API documentation for endpoint details
4. Implement your integration or use our SDKs
5. Test with staging environment before production

Example Request

POST /api/public/releases
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "title": "Album Title",
  "type": "album",
  "primary_artist": "Artist Name",
  "release_date": "2024-03-15",
  "tracks": [
    {
      "title": "Track One",
      "track_number": 1,
      "isrc": "USRC12400001"
    }
  ]
}

Recording Your Previous Distributor

When you’re migrating releases that are already live elsewhere, the public Releases API accepts an optional transfer_from_distributor field (free text, up to 255 characters) to record the distributor you’re moving from. It becomes read-only once the release is distributed, so set it before or at submission.

API Benefits

• Full automation - No manual intervention required
• System integration - Connect with your DAM, CRM, or other tools
• Scheduled releases - Queue releases for future distribution
• Custom validation - Pre-validate content before submission
• Webhook notifications - Get real-time updates on delivery status
• Error handling - Programmatic error detection and retry

Rate Limits

The API has rate limits to ensure system stability. See the API Overview for current rate limit details.

See API Overview for complete documentation.

---

DDEX Import

Overview

DDEX (Digital Data Exchange) is the industry-standard format used by major labels for delivering content to distributors. LabelGrid supports DDEX import for enterprise clients who already have DDEX delivery infrastructure.

What is DDEX?

DDEX is an XML-based standard that packages:

• Release metadata
• Track information
• Audio file references
• Artwork and assets
• Deal terms and territories

Supported Formats

Version	Status
ERN 4.3.2	Supported (recommended)
ERN 4.3.1	Supported
ERN 4.3.0	Supported
ERN 3.8.2	Supported (legacy)

DDEX Setup Process

1. Contact support to request DDEX enablement
2. Complete onboarding with our technical team
3. Configure delivery settings and file paths
4. Set up SFTP credentials for secure file transfer
5. Submit test delivery for validation
6. Begin production deliveries once approved

Delivery Workflow

Your System → DDEX XML + Assets → SFTP Upload → LabelGrid Processing → Distribution

DDEX Requirements

Requirement	Details
Plan	API access enabled (contact support)
Format	ERN 4.3.2 preferred (4.3.1, 4.3.0, and 3.8.2 also supported)
Delivery	SFTP only
Assets	Audio files included or referenced
Validation	Pre-flight validation recommended

When to Use DDEX

DDEX import is ideal if:

• You already have DDEX delivery infrastructure
• You’re migrating from another distributor that uses DDEX
• Your content management system exports DDEX natively
• You’re a major label or large independent with established workflows

When to Use API Instead

The REST/JSON API is better if:

• You’re building a new integration from scratch
• You prefer modern web APIs over XML
• You need real-time bidirectional communication
• You want webhook-based notifications

---

Choosing Your Method

Factor	API Integration	DDEX Import
Setup complexity	Lower	Higher
Existing infrastructure	Build new	Use existing DDEX
Format	JSON	XML
Delivery method	HTTPS	SFTP
Real-time updates	Yes (webhooks)	Polling required
Best for	New integrations	Enterprise migration

---

Processing Times

Once content is uploaded via API or DDEX, processing time depends on:

• Number of releases and tracks
• Audio file sizes
• Metadata complexity
• Current system load

Larger catalogs naturally take longer to process. Contact support if you need guidance on expected timelines for your specific catalog size.

---

Submission Limits for Large Migrations

Large migrations can hit a rolling submission cap that counts API and DDEX imports too — see Catalog & release limits for how it works. Before a big one-time migration, contact support so we can arrange a temporary bypass window rather than you running into the cap mid-migration.

Verify all tracks ingested

After a bulk or DDEX import, confirm every track imported correctly before you distribute.

---

FAQ

”How do I migrate a large catalog to LabelGrid?”

Use bulk upload — API integration (for automated, custom workflows) or DDEX import (for industry-standard feeds and distributor-scale migrations). Both require API access enabled on your plan. Reuse your existing ISRCs and UPCs with exactly matching metadata so DSPs preserve your streams, saves, and playlists, and upload to LabelGrid before taking your catalog down from the old distributor.

”Can LabelGrid import my catalog via DDEX?”

Yes. LabelGrid supports DDEX import (ERN 4.3.2 recommended; 4.3.1, 4.3.0, and 3.8.2 also supported) over SFTP for clients with existing DDEX delivery infrastructure. Contact support to enable it. LabelGrid supports the DDEX standard but is not a DDEX consortium member.

”Which DDEX ERN versions does LabelGrid support?”

LabelGrid supports DDEX ERN 3.8.2, 4.3.0, 4.3.1, and 4.3.2, with 4.3.2 recommended for new deliveries. LabelGrid supports these standards and is not a DDEX consortium member.

”Will my streams and playlists carry over when I migrate a large catalog?”

Yes, if you reuse the same ISRCs and UPCs with exactly matching metadata. DSPs match content by ISRC and UPC, so identical codes and metadata let them merge your catalog with the existing releases and keep your streaming history, saves, and playlist placements.

”What are the submission limits for a big one-time migration?”

Large migrations count against a rolling submission cap that includes API and DDEX imports. Before a big migration, contact support to arrange a temporary bypass window so you do not hit the cap mid-migration.

---

Related

Managing a large catalog? See catalog management on our website for how LabelGrid keeps your releases organized at scale. See also Transferring Your Catalog.

---

Need Help?

For bulk upload setup assistance:

• API integration: See API Overview or contact support
• DDEX enablement: Contact our support team with your requirements

Our team can help you choose the right method and guide you through setup.