# How to Automate Spotify Audience Segmentation for Your CRM using the API - Tool: API Automations - Difficulty: Advanced - Fix time: 1-2 hours - Compatibility: OAuth 2.0 — Development Mode (max 5 authorized users, app owner must have Spotify Premium). Production requires Extended Quota Mode (250,000+ MAU organization). - Last updated: May 2026 ## TL;DR Match Spotify listener data to CRM contacts using GET /v1/me (user-read-email scope) to retrieve the authorized user's email, then GET /v1/me/top/artists for genre/taste segments. Critical limitation: Spotify has NO server-to-server 'find user by email' lookup. CRM matching requires each listener to individually OAuth-authorize your app. Development Mode caps you at 5 authorized users — production scale requires Extended Quota Mode, which since May 2025 requires a legally registered organization with 250,000+ monthly active users. ## Best practices - Be upfront with users about what Spotify data you're accessing — display the scope permissions on your Connect Spotify page before they authorize - Store a spotify_connected_at timestamp and spotify_last_synced timestamp on each CRM contact to track data freshness - Handle the case where a user's Spotify email differs from their CRM email by matching on spotify_user_id instead of email after initial connection - Gracefully handle missing email (some Spotify accounts do not have an email address) by falling back to matching on the CRM contact ID passed through the state parameter - Limit the CRM tags you create to a manageable number — genre tags like 'music_genre:post-grunge' are actionable; storing all 50 raw genres as tags creates noise - Test your full OAuth flow with a real user account in Development Mode before requesting Extended Quota — many bugs surface during the redirect and callback phase - Implement a user-facing 'Disconnect Spotify' option that revokes access tokens and clears stored segments — it's legally required under GDPR and builds trust ## Frequently asked questions ### Can I look up a user's Spotify data by their email address without them authorizing my app? No — this is the single most important limitation for CRM use cases. Spotify has no server-to-server 'find user by email' API. The only way to access a user's listening data is for that user to individually complete the OAuth authorization flow on your website or app. After they authorize, you can call GET /v1/me with user-read-email scope to retrieve their Spotify email and match it to your CRM. ### How many users can I segment in Development Mode? Only 5 authorized Spotify users per Client ID in Development Mode (as of February 11, 2026). The app owner must have Spotify Premium. You must manually add each test user at developer.spotify.com/dashboard before they can authorize. For production audience segmentation at real scale, Extended Quota Mode is required — which since May 15, 2025 requires a legally registered organization with 250,000+ monthly active users. ### Is the Spotify API free for audience segmentation? Yes — the API itself is free. But Development Mode is limited to 5 users, making it unsuitable for production segmentation campaigns. Extended Quota Mode requires a legally registered organization with 250,000+ MAU — this is a hard requirement, not a paid tier. There is no paid plan to purchase more Development Mode slots. ### What happens when I hit the rate limit? You receive HTTP 429 with a Retry-After header. At scale (Extended Quota), concurrent user syncs compound the rolling 30-second rate limit. Process batch re-syncs sequentially with 500ms delays between users rather than running them concurrently. Always honor the Retry-After header value exactly. ### Can I use audio features (tempo, energy, danceability) for more precise segmentation? No — GET /v1/audio-features is permanently deprecated for apps created after November 27, 2024 and returns HTTP 403. Use genre tags from GET /v1/me/top/artists as the primary segmentation signal. Genre tags like 'post-grunge', 'dance pop', or 'lo-fi beats' provide meaningful taste segmentation without audio features data. ### What data protection obligations apply when storing Spotify listening history in a CRM? Listening history is personal data under GDPR and similar regulations. You must: disclose what Spotify data you collect in your privacy policy, obtain explicit consent via the OAuth flow, provide a way for users to disconnect and have their data deleted, and store tokens and listening data securely (encrypted at rest). Do not sell or share Spotify listening data with third parties without explicit consent. Spotify's Developer Terms also have their own data use restrictions. ### Can RapidDev help build a production Spotify CRM segmentation system? Yes — RapidDev has built 600+ integrations including OAuth flows, CRM connectors, and audience segmentation systems. We can build a complete 'Connect Spotify' feature with secure token storage, monthly re-sync, CRM tag management, and compliance tooling. Reach out at rapidevelopers.com for a free consultation. --- Source: https://www.rapidevelopers.com/api-automations/how-to-automate-spotify-audience-segmentation-for-your-crm-using-the-api © RapidDev — https://www.rapidevelopers.com/api-automations/how-to-automate-spotify-audience-segmentation-for-your-crm-using-the-api