spotify-ads-api

spotify-ads-api

A Claude Code plugin that lets you manage Spotify advertising campaigns through natural language. Create campaigns, target audiences, launch ads, and pull performance reports — all by describing what you want in plain English.

Check out our post on the Spotify Engineering Blog.

Prerequisites

• Claude Code CLI
• A Spotify Developer account with an ads-enabled app
• A Spotify Ads ad account ID
• Python 3.8+ (for automated OAuth flow; optional — manual flow available as fallback)

Quick Start

Option A: Install from registry (recommended)

claude plugin i spotify-ads-api

Option B: Install from source (for local development / testing)

1. Clone the repository:

   git clone https://github.com/spotify/ads-claude-plugin.git
   

2. Launch Claude Code with the plugin directory:

   claude --plugin-dir /path/to/ads-claude-plugin
   

   The --plugin-dir flag loads the plugin for that session only. You can also add it to a shell alias if you use it frequently:

   alias claude-ads='claude --plugin-dir /path/to/ads-claude-plugin'
   

Configure

1. Set up the redirect URI in Spotify Developer Dashboard:

   • Go to developer.spotify.com and open your app settings
   • Under Redirect URIs, add: http://127.0.0.1:8080/callback
   • Save the changes
   • Open https://adsmanager.spotify.com/api-terms and make sure the ad account you want to use is selected. Accept the terms to authorize your client id to access your ad account through Ads API.

2. Configure OAuth credentials:

   /spotify-ads-api:configure
   

   This opens your browser for Spotify authorization, then saves your tokens locally with automatic refresh.

3. Create your first campaign:

   /spotify-ads-api:build-campaign Create an audio campaign called Summer Promo targeting US listeners aged 25-44 with $100/day budget
   

Authentication

The plugin supports three authentication modes:

OAuth 2.0 (Recommended)

Run /spotify-ads-api:configure or /spotify-ads-api:configure oauth. This launches an automated OAuth flow using a local Python script. Your tokens are stored locally and refresh automatically before API calls.

Manual OAuth

Run /spotify-ads-api:configure manual if Python is not available. You'll manually open the authorization URL, copy the redirect, and the plugin exchanges the code for tokens via curl.

Direct Token (Legacy)

Run /spotify-ads-api:configure token <your-token>. Accepts a pre-obtained access token. No automatic refresh — token expires in ~1 hour.

Available Skills

Skill	Description
/spotify-ads-api:configure	Set up OAuth credentials, ad account, and preferences
/spotify-ads-api:campaigns	List, create, get, or update campaigns
/spotify-ads-api:ads	Manage ad sets and ads (list, create, get, update)
/spotify-ads-api:build-campaign	Create a full campaign hierarchy from a plain-text description
/spotify-ads-api:report	Pull aggregate metrics, audience insights, or async CSV reports
/spotify-ads-api:assets	Upload, list, and manage creative assets
/spotify-ads-api:dashboard	Quick performance overview of active campaigns

Natural Language Examples

The plugin includes an agent that interprets natural language requests automatically:

• "Create a campaign called Summer Sale with a reach objective"
• "Set up an audio ad targeting 18-34 year olds in the US with $50/day budget"
• "Show me impressions, spend, and clicks for all campaigns last month"
• "Pause the Summer Sale campaign"
• "Generate a CSV report of daily spend by campaign for January"
• "Build me a complete audio campaign targeting US listeners aged 25-44"
• "Upload my-audio.mp3 as a creative asset"
• "How are my campaigns performing?"

Configuration Reference

Settings are stored in .claude/spotify-ads-api.local.md (gitignored):

Field	Description	Default
access_token	OAuth2 bearer token	—
refresh_token	Token for automatic renewal	—
token_expires_at	ISO 8601 expiry timestamp	—
client_id	Spotify app client ID	—
ad_account_id	Default ad account UUID	—
auto_execute	Skip confirmation prompts	false

The client secret is stored in the macOS Keychain (not in the settings file) for security. It is saved during /spotify-ads-api:configure and retrieved automatically by the token refresh hook.

Troubleshooting