Last June, we introduced support for TikTok’s new Scanning service (TTS)— and it’s officially going live. This feature lets users set Monetize
or BlockAccess
policies on tracks used in UGC videos.
To comply with TikTok’s scanning policies, the following fields must be included per track:
Monetize
– Allow monetized UGC usageBlockAccess
– Prevent UGC use entirelyTracks without updates after the deadline will be excluded from scanning and monetization
/content/release/save
/content/release/retail/save
2025-03-31
Tiktok Deadline for the new Scanning service (TTS) API documentation Release Notes have been updated and renamed to Changelog.
Deezer is enforcing new contributor metadata requirements starting Q2 2025. Tracks missing required roles will be removed, along with associated albums.
/distribution/release/multiresendtostore
/distribution/release/addtoqueue
/distribution/release/approve
2025-04-14
Global compliance deadline 2025-05-31
Brazil (BR country code) compliance deadline A profileId of 0
, null
, or an absent entry in the artistExternalIds
array will now be treated the same. The specific behavior of this empty state will differ depending on the store.
Any endpoints responding with an Artist Object will have its artistExternalIds
array contain only existing external IDs. Values that were previously had "profileId": 0
will no longer appear in the array.
/artists
/artists/summary
/artists/{artistId}
/content/release/save
/content/release/all
/content/release/{releaseId}
2025-03-11
Added support for additional DSPs when it comes to providing Artist External IDs.
/artists
/artists/summary
/artists/{artistId}
/content/release/save
/content/release/all
/content/release/{releaseId}
We no longer support testing on the staging environment. All of the examples and documentation were updated to reflect this change.
Please contact us to create a dedicated Sandbox account.
2025-02-05
We are removing support for redirecting to, and generally using, the outdated V1 Web Interface.
2025-02-05
From this point forward the only supported url will be api.revelator.com
This is currently not a breaking change, but we recommend updating your code to use the primary url, as others might become deprecated in the future.
2025-02-05
Added support for Engagement Analytics to the V3 Analytics. 📊
engagement
metric/analytics/{metric}/{aggregation}
Dolby atmos is officially supported and ready to be distributed.
To supported this change, the Track Object has been updated. Explore the new changes directly on the Track Object and refer to the New track recording model section for more information.
Make sure you understand the limitations and cost associated with Dolby Atmos recordings before creating tracks. Read our Dolby Atmos Guide for more information.
/content/release/save
/content/release/all
/content/release/all/summary
/content/release/{releaseId}
As part of our security hygiene and access protocol work, we’ve moved to a more secure token protocol and updated the related documentation accordingly.
The access token can only be provided in the Authorization header, and must be prefixed with the word “Bearer”. (Bearer token)
2024-08-05
Added this previously undocumented field to the Artist Object.
/content/release/save
/content/release/all
/content/release/{releaseId}
/artists
/artists/summary
/artists/{artistId}
Newly documented Takedowns section.
Added the Common Resources section in order to provide easy-access and overview of this type of data.
New Monetization Policy changes introduced to reflect TikTok’s Monetization Changes
NoTikTokScanning
, Monetize
, BlockAccess
)trackMonetizationPolicyIds
available during Setting Distribution Options for track-level policies./content/release/retail/save
New fields/changes introduced to reflect TikTok’s Monetization Changes
trackProperties
is a new and required field on the Track Object.trackType
is now a required field on the Track Object. This field also accepts a new value: 2
- Cover song/content/release/save
/content/release/all
/content/release/all/summary
/content/release/{releaseId}
/distribution/release/{releaseId}/validate
/distribution/release/addtoqueue
2024-07-15
Implementation deadline Attemnts to distribute to stores containing the isActive == false
will now fail.
/distribution/release/multiresendtostore
/distribution/release/addtoqueue
/distribution/release/approve
2024-05-22
Added the (Beta) API support for user invites.
Composer/Writer details on tracks missing either a valid first and last artist name are no longer allowed for distribution.
/distribution/release/multiresendtostore
/distribution/release/addtoqueue
/distribution/release/approve
2024-05-15
Tracks that are less than 2 seconds long are no longer allowed for distribution. Any attempt at distributing or uploading these tracks will fail.
/distribution/release/multiresendtostore
/distribution/release/addtoqueue
/distribution/release/approve
/media/audio/*
2024-05-15
Added a Glossary page containing most used terms.
Royalty tokens are now supported and documented.
Distribution statuses updated.
/distribution/store/all
2024-03-20
The endpoint examples are now back after the documentation migration.
Tipalti integration added to Revelator. By completing the following flows you will be able to pay your payees using this feature:
CTRL + K
)Using an externalUrl
to associate files with a track/release is no longer recommended! Files referenced like this are not being downloaded by our system until distribution, leading to unexpected behavior. Use the endpoints mentioned above for all file uploading needs.
/content/release/save
2023-11-11
Newly documented endpoints for uploading files
POST /media/audio/upload/wav
- Upload a file in wav format to the Revelator serversPOST /media/image/upload
- Upload an image file to the Revelator serversPOST /media/audio/pullexternal/wav
- Pull a file in wav format from an external url to the Revalator serversPOST /account/createnewaccount'
- endpoint is now deprecated. This is done to mitigate confusion for creating new accounts.
/account/createnewaccount
2023-09-26
Enterprise information endpoints:
GET /enterprise/clients/{id}
- Retrieves basic information about a single enterpriseGET /enterprise/clients/all
- Retrieves basic information about all enterprises associated with the account