All track results now have a work
node that references the its optional associated work.
All album and track results now have an identifiers
node array contaning the custom identifiers available for that resource. For exemple ASCAP Code, YouTube Asset Identifier, ABRAMUS Code, etc.
New endpoint to list / search for works added :
This is now possible to upload a reference audio file via this new endpoint : https://docs.reprtoir.com/reference/post_api-reference-audios
In your Reprtoir Settings, under Integrations > Webhooks, you can register a webhook URL to be called when an upload is ready to be used in a search.
Then in the tracks search endpoint, when using search_mode=similarity
and search_by_similarity[source]=audio
, the UUID of the reference audio can be passed to search_by_similarity[reference_uuid]
to search for tracks similar to the uploaded audio file.
The following endpoint has been updated:
https://docs.reprtoir.com/reference/get_api-audios-uuid
It now returns an new waveform
object that includes an URL to the raw waveform data of the audio.
In addition of the MP3 320 kbps version we already sent within the API, we have added the MP3 128 kbps version.
The following endpoint has been updated:
It now returns an additional field bitrate
in the versions
array of audio files.
We have added the ability to search fo similar tracks from the API by adding the similarity
value inside the search_mode
parameter of the following endpoints:
- https://docs.reprtoir.com/reference/get_api-tracks
- https://docs.reprtoir.com/reference/post_api-tracks-search
This search mode requires that your account is subscribed to our Audio AI add-on.
When defining your search_mode
as similarity
, please make sure you fill in the new search_by_similarity
object on the request.
- The keys
original_title
anddescription
have been added on Album schema. - The key
description
has been added on Track schema.
We added the weight
key on Audio AI tags of a resource. This weight
key will only appears in the response for all Audio AI tag categories, except Augmented Keywords which does not have this information.
Example:
"tag_categories": [
{
"uuid": "4729da4e-ebe4-45d8-a09f-5b950ea890ff",
"name": "Instruments",
"tags": [
{
"uuid": "6ed82a4f-7060-4945-9559-ff4f80d304b5",
"name": "Electric Guitar",
"weight": 92
},
{
"uuid": "dfdf39f7-fb7a-4e3d-9ecb-95b0a269f759",
"name": "Percussion",
"weight": 96
}
]
},
...
]
Our first API version (2024-04-11) is publicly available.
This version is at the moment read-only and allows your to retrieve and search for primary CMS assets.