Skip to content

Fix Beatport search after __NEXT_DATA__ removal - #523

Open
Simon-Zwa wants to merge 3 commits into
Marekkon5:masterfrom
Simon-Zwa:master
Open

Fix Beatport search after __NEXT_DATA__ removal#523
Simon-Zwa wants to merge 3 commits into
Marekkon5:masterfrom
Simon-Zwa:master

Conversation

@Simon-Zwa

Copy link
Copy Markdown

Beatport no longer exposes NEXT_DATA on search pages, causing search failures.

Updated Beatport search to use the v4 catalog API endpoint instead of scraping the website.

Adjusted deserialization to support the new API response format (tracks array).

Beatport no longer exposes __NEXT_DATA__ on search pages, causing search failures.

Updated Beatport search to use the v4 catalog API endpoint instead of scraping the website.

Adjusted deserialization to support the new API response format (tracks array).
TX-RX added a commit to TX-RX/onetagger that referenced this pull request Jul 8, 2026
…am PR Marekkon5#523) (#1)

* Fix Beatport search after __NEXT_DATA__ removal

Beatport no longer exposes __NEXT_DATA__ on search pages, causing search failures.

Updated Beatport search to use the v4 catalog API endpoint instead of scraping the website.

Adjusted deserialization to support the new API response format (tracks array).

* Update README with temporary Beatport fix note

Added a note about a temporary Beatport fix for May 2026.

---------

Co-authored-by: Simon-Zwa <simonmcc30@gmail.com>
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

Successfully merging this pull request may close these issues.

1 participant