# How to Automate Spotify Song Recommendations using the API - Tool: API Automations - Difficulty: Intermediate - Fix time: 30-60 minutes - Compatibility: OAuth 2.0 — Development Mode (max 5 authorized users, app owner must have Spotify Premium) - Last updated: May 2026 ## TL;DR GET /v1/recommendations is permanently deprecated for Spotify apps created after November 27, 2024 (returns 403). The working alternative: use GET /v1/me/top/tracks and GET /v1/me/top/artists to get seed data, then GET /v1/search with genre and artist keywords to discover similar tracks, and POST /v1/playlists/{id}/tracks to save results. This approach requires 10-20 search queries per session — throttle to 3 requests/second to stay within the rolling 30-second rate limit. ## Best practices - Be explicit in your app about the fact that /recommendations is deprecated — users who research this topic will encounter broken tutorials and appreciate clarity - Prioritize genre-based searches over artist-based searches for discovery — artist searches tend to return the same well-known tracks the user already knows - Filter out tracks from your top tracks (medium_term) not just recently played — medium_term covers 6 months and prevents re-recommending familiar favorites - Mix popularity ranges in your selection algorithm: take 15 high-popularity tracks (score >65) and 15 mid-popularity tracks (40-65) for a balance of popular and niche discoveries - Add a year filter to genre searches (e.g., year:2020-2026) to prioritize contemporary releases over decades-old catalog tracks - Validate that all track URIs are in the correct format (spotify:track:{22-char-id}) before adding to playlists — malformed URIs cause silent failures ## Frequently asked questions ### Why does GET /v1/recommendations return 403? GET /v1/recommendations was permanently deprecated for Spotify apps created after November 27, 2024. If your app was created after that date, this endpoint will always return HTTP 403 and there is no workaround. Apps that existed before that date with Extended Quota Mode are grandfathered. The working alternative is to use GET /v1/me/top/artists to extract genre seeds, then run GET /v1/search queries with those genres to discover tracks. ### What other Spotify endpoints are deprecated for new apps? As of November 27, 2024, these endpoints return 403 for new apps: GET /v1/recommendations, GET /v1/audio-features/{id} (and batch), GET /v1/audio-analysis/{id}, GET /v1/artists/{id}/related-artists, GET /v1/browse/featured-playlists, GET /v1/browse/categories/{id}/playlists. The preview_url field is also no longer populated. Additionally, as of February 2026, Development Mode apps have restrictions on artist popularity scores, follower counts, top-tracks per artist, and new-releases browsing. ### Is the Spotify API free? Yes — the Spotify Web API is free to use. Development Mode limits you to 5 authorized users per Client ID (as of February 11, 2026) and requires the app owner to have Spotify Premium. Extended Quota Mode for production apps requires a legally registered organization with 250,000+ monthly active users as of May 2025. ### What happens when I hit the rate limit? You receive HTTP 429 with a Retry-After header in seconds. The search-based recommendation approach uses 10-20 search queries per run, which can hit the rate limit if run too quickly. Add 333ms delays between search requests (3 per second) and honor the Retry-After header when 429 is received. ### Can I use audio features (tempo, energy, danceability) to filter recommendations? No — GET /v1/audio-features is deprecated for apps created after November 27, 2024 and returns 403. You cannot access tempo, energy, danceability, valence, or any other audio analysis properties. The primary filtering signals available to new apps are: genre (from artist data), popularity score (proxy for mainstream-ness), and release year (from album data). ### Can RapidDev help build a custom Spotify recommendation engine? Yes — RapidDev has built 600+ integrations and can design a production recommendation pipeline using the search-based approach that works for all Spotify apps. We can also integrate third-party audio analysis APIs (like Tunebat or AcousticBrainz) as replacements for the deprecated audio features. Reach out at rapidevelopers.com for a free consultation. ### Are there third-party alternatives for audio features data since Spotify deprecated it? Yes — several options exist: Tunebat.com offers a paid API with BPM, key, and energy data for Spotify tracks. AcousticBrainz (open-source, though the main service is shutting down) provided similar data. Some developers use the Essentia library locally to analyze audio files. None are as convenient as Spotify's native audio features API was, but they fill the gap for apps that need acoustic property data. --- Source: https://www.rapidevelopers.com/api-automations/how-to-automate-spotify-song-recommendations-using-the-api © RapidDev — https://www.rapidevelopers.com/api-automations/how-to-automate-spotify-song-recommendations-using-the-api