Adding redirects to API download URLs

[Alastair Porter]

Hi everyone,

From October 1 2026, a request to the following endpoints MAY result in a response of an HTTP 302 when making a download request, redirecting to the actual location where the sound file can be downloaded.

/apiv2/sounds/<id>/download/ 

/apiv2/packs/<id>/download/

/apiv2/download/<token>/

If your applications cannot handle redirect responses then please update it to do so. We may only send these responses in case of high load on freesound, so make sure that you can support both schemes.

We apologise for the very short notice on this change, we need to urgently make these changes in order to mitigate ongoing attacks against freesound.

If you have a deployed application that cannot handle redirect codes and is difficult to update then please reach out to us via your normal support channel to see how we can accommodate you.

Thanks,

Alastair