Search `/tracks` endpoint cannot send both `created_at` and `bpm`

[marcaaron]

Thanks for opening the API up again!

Was messing around and noticed that it's unclear whether it's possible to use created_at and bpm at the same time?

e.g.

Only bpm

https://api.soundcloud.com/tracks?
  q=house
  &bpm[from]=0
  &bpm[to]=300
  &limit=50
  &offset=0
  &linked_partitioning=true

Only created_at

https://api.soundcloud.com/tracks?
  q=house
  &created_at[from]=2025-07-03 06:54:54
  &created_at[to]=2025-07-10 06:54:54
  &limit=50
  &offset=0
  &linked_partitioning=true

But when user together the track collection will be empty...

https://api.soundcloud.com/tracks?
  q=house
  &bpm[from]=0
  &bpm[to]=300
  &created_at[from]=2025-07-03 06:54:54
  &created_at[to]=2025-07-10 06:54:54
  &limit=50
  &offset=0
  &linked_partitioning=true

Is this expected?

[youssefhassan]

Hey @marcaaron, thanks for reaching out

If the two queries have at least one track in common, this should return the intersection of both results.

Let us know if that is not the case, so we can dig deeper