spot auth and spot alias commands to manage it interactively.
Config file location
spot auth. If the file doesn’t exist, spot uses empty defaults.
File format
Fields
| Field | Description |
|---|---|
client_id | Your Spotify app’s client ID |
client_secret | Your Spotify app’s client secret |
[aliases] | Key-value alias mappings (optional) |
client_id and client_secret come from a Spotify app you create at developer.spotify.com/dashboard. Both are required for search commands (spot search, spot <query>). Playback controls (spot pause, spot next, spot vol, etc.) use AppleScript and do not require credentials.
[aliases] maps short names to full search queries. Each entry is alias-name = "search query". When you run spot <alias>, spot substitutes the full query before searching.
Run
spot auth to set credentials interactively instead of editing the file directly. Run spot auth --status to verify your credentials are valid.Token cache
spot caches the Spotify API access token to avoid an HTTP round-trip on every command.| Property | Value |
|---|---|
| Location | ~/.config/spot/token.json |
| TTL | 1 hour (auto-refreshed) |
token.json manually — if you encounter token errors, delete the file and run spot auth again.
Managing credentials
Create a Spotify app
Go to developer.spotify.com/dashboard and create a new app to get your Client ID and Client Secret.
Run spot auth
Managing aliases
Aliases let you create short names for frequent searches.[aliases] in config.toml and resolved before search, so spot white-album plays “The Beatles”.