Changelog

The maximum file size for audio uploads has increased to 5 GB.

The maximum file size for video uploads has increased to 30 GB.

previewStartSeconds can now be set to 0. Previously, the value had to be null or greater than 0.

Introduces the Composers endpoints to manage writer identities referenced from tracks.

See Composers.

Introduces the endpoints that move a release onto stores and back off again. Both take a list of distributorStoreIds and return a bare boolean meaning the request was accepted—not that the work is done.

Delivering does not publish a release: it submits the release into the inspection queue, where an inspector from your organization must approve it in the Revelator UI before anything is packaged and sent to a DSP.

See Delivery & Takedown.

Introduces the Labels endpoints to manage record label profiles referenced from releases, tracks, and artists.

See Labels.

lastUpdateDateFrom and lastUpdateDateTo are now available on physical release and artists listings. Both take a UTC date-time and filter on when the record was last modified, which makes incremental catalog syncs possible without paging the full collection.

Introduces the Publishers endpoints to manage the publishers referenced from tracks as the rights holder behind a composer’s share.

See Publishers.

Introduces the Releases endpoints to manage the releases that group catalog assets for distribution.

See Releases.

Adds single-asset validation for tracks and videos, complementing the release-level deliver/validate and takedown/validate endpoints. Each checks the asset’s own metadata—identifiers, without evaluating the release it belongs to. This makes it possible to check a track or video while it is still being prepared, before it is added to a release.

See Validations.

Introduces the Tracks endpoints to manage individual audio recordings and the credits attached to them.

See Tracks.

Extends rights management to videos. Streaming, Download, and UGC rights can now be read and set per video, alongside the track- and release-level rights already available.

See Rights.

Introduces the Videos endpoints, making video a first-class catalog asset with its own metadata, credits, and rights. Videos are distributed by assigning them to a release exactly like tracks.

See Videos.

Added physicalReleaseIds, assetIds, artistIds, and labelIds filters to physical release listings.

See Physical Releases.

Added validation endpoints for checking a release without changing anything. deliver/validate reports what would block distribution; takedown/validate reports whether the release can be taken down from the given stores. Both return hasBlockingErrors, which is the same flag the corresponding action checks—false means that action will not be rejected by validation.

See Validations.

Starting July 29, 2026, the releasesCount and tracksCount fields will be removed from artist responses across all affected endpoints.

These fields were previously exposed as part of the artist object but are no longer reliable and have been removed to prevent incorrect or inconsistent data usage.

Updates the behavior of Facebook DSP profile handling through the externalIds property.

Previously, providing only one Facebook profile automatically created the corresponding entry for the other profile. Starting July 29, 2026, both Facebook profile entries must be managed together. Omitting either entry will be treated as an instruction to remove the corresponding profile association.

Introduces the Artists endpoints to manage individual and group act metadata. These endpoints supports rich profile data including biographies, localizations, and social media links. It also features robust management of External Artist IDs for DSP profile mapping (preventing catalog fragmentation on platforms like Apple, Spotify, and Meta) and support for the Spotify Artist Profile Protection key.

The labelId property is no longer required when creating or updating physical releases. If a label is not applicable to your release, you can now safely omit this field from your request payload or pass null.

Introduces the read-only YouTube API. These endpoints allow you to search, filter, and retrieve rich metadata and performance statistics for YouTube channels and videos that have been synced with your Revelator account.

We have updated the global API rate limiting policy to provide a smoother developer experience and more accurate traffic measurement.

• Rolling Window: The 200 requests/minute limit is now evaluated using a continuous 60-second rolling window instead of a fixed calendar-minute window.
• Reduced Ban Time: If the rate limit is exceeded, the temporary IP block (resulting in 429 Too Many Requests) has been reduced from 1 hour down to 10 minutes.

You can now subscribe to our API Changelog via RSS!

If you want to stay informed about breaking changes, new endpoints, and platform updates in real-time, you can plug our RSS feed into your favorite RSS reader, Slack workspace, or automated notification workflow.

To subscribe, click the RSS Feed button at the top of the changelog page, or point your reader directly to https://api-docs.revelator.com/v2/rss.xml.

To ensure platform stability and performance, we have introduced a global rate limit for the V2.0 API.

The API now strictly enforces a limit of 200 requests per minute per IP address (evaluated on a fixed 1-minute window). If this limit is exceeded, the offending IP address will be temporarily blocked for 1 hour. Any requests made during this ban period will be rejected with a standard HTTP 429 Too Many Requests response.

We strongly recommend implementing exponential backoff in your API clients to prevent unintended bans during bulk operations.

We are excited to introduce our new Model Context Protocol (MCP) servers in Public Beta. This suite of five servers (Catalog, Supply Chain, Analytics, Royalties, and Blockchain) enables you to securely connect AI assistants (like Claude Desktop) directly to your Revelator data.

By configuring these servers, your LLMs can use natural language to query catalog metadata, analyze Top Movers and revenue, manage physical releases, and more.

Note: Our MCP Servers are currently in BETA. They are under active development and are subject to breaking changes - some tools can result in 403 Forbidden or other errors.

Introduces a new multipart upload workflow for securely uploading binary files (audio, video, images, and documents). This API allows for optional chunk splitting and parallel uploads to significantly increase upload speeds. Files uploaded via these endpoints generate a fileUrl that can be referenced across V2.0 API payloads.

Introduces the Physical Releases API to manage metadata for physical music and video products (e.g., Vinyl, CD, DVD, Blu-ray). This API allows you to link existing digital catalog assets to physical product formats based on category-specific configurations. Note: This is a metadata-only feature and does not support manufacturing, inventory, or physical supply chain workflows.

Introduces the Top Movers analytics endpoint. This API allows you to retrieve rising and falling trends across specific dimensions (labels, artists, releases, tracks, DSPs, and markets). It calculates stream and revenue momentum by comparing specific periods (daily, weekly, monthly, quarterly, yearly) against their preceding equivalent periods. Built-in thresholds automatically filter out low-volume statistical noise.

The request body structure has been updated to align with the GET response format. Instead of a flat array of IDs, you must now group prices by distributorStoreId and separate them into trackPrices and releasePrices arrays.

The request body structure has been updated to align with the GET response format. You must now submit policies within a monetizationPolicies array of objects (e.g., { "monetizationPolicyId": 5 }) rather than a simple array of integers.

Enables granular management of monetization policies. Unlike previous API versions, this update supports setting unique policies for individual tracks across specific UGC stores (YouTube Content ID, TikTok, Facebook).

New endpoints to retrieve and configure pricing. The API now dynamically filters available pricing options based on the release’s audio quality (Bit Depth/Sample Rate) and specific DSP configuration.

Introduces a new structure for defining Availability Rules. You can now define precise inclusion and exclusion logic for specific territories and DSPs at both the Release and Track levels.

Introduces new endpoints to manage Streaming, Download, and UGC rights. This API allows for granular control, including setting specific download permissions at the release level and full rights management at the individual track level.