Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beastsaber feeds are not working #57

Open
YoukaiTheGit opened this issue May 8, 2024 · 1 comment
Open

beastsaber feeds are not working #57

YoukaiTheGit opened this issue May 8, 2024 · 1 comment

Comments

@YoukaiTheGit
Copy link

In version 1. 0.1.0, none of the sync sources that use beastsaber (Bookmarks, Follows, or CuratorRecommended) are working, with their APIs returning 404 from bsaber.com. The current API's being queried and returning 404 are (e.g.):

https://bsaber.com/wp-json/bsaber-api/songs/?bookmarked_by=Youkai&page=1&count=50
https://bsaber.com/wp-json/bsaber-api/songs/?followed_by=Youkai&count=50&page=1
https://bsaber.com/wp-json/bsaber-api/songs/?bookmarked_by=curatorrecommended&page=1&count=50

Sample log attached

log.txt

@VidFerris
Copy link

After looking into this, Beast Saber is phasing out its API, so only the Beat Saver API will be available going forward. An equivalent API endpoint to the old Curated one on Beast Saber is at is at https://api.beatsaver.com/maps/latest?sort=CURATED. Full Beat Saver API docs are at:

https://api.beatsaver.com/docs/index.html?url=./swagger.json

In case it helps you, the following python code is my hacked-together replacement for BeatSync which hits the appropriate Curated endpoint and does some basic checking to ensure it doesn't redownload maps with duplicated hashes. I only ever used the Curator feed so that's enough for my use case.

https://gist.github.com/VidFerris/e90c6cde98ef3f203843edf176ce1449

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants