Changelog

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.

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.

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 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. You must now submit policies within a monetizationPolicies array of objects (e.g., { "monetizationPolicyId": 5 }) rather than a simple array of integers.

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.

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 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.

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).

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.