Spotify | Operate As Docs

Connect your client's Spotify with a sign-in, and call its API through Operate As.

Website: spotify.com
Connects by: Signing in with Spotify
Category: Social and video
Services: 1
Tools: 88

Service	Key	Base URL
Spotify	`spotify`	`https://api.spotify.com/v1`

Connecting

Your client presses Connect on their link and approves on Spotify's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "spotify"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "spotify"    ]  }]

Permissions

What the client reads	Permission it asks for
See your Spotify profile	`user-read-private`
See your playlists	`playlist-read-private`
Create and change your playlists	`playlist-modify-private`

Tools

Install Spotify's typed package for your language:

pip install operate-as-spotify

pip install operate-as-spotify

Run spotify.add_to_queue

curl -X POST https://api.operate.as/v1/actions/spotify.add_to_queue \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "uri": "<uri>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/spotify.add_to_queue \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "uri": "<uri>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/spotify.add_to_queue

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.spotify.com/v1. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../spotify/me" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../spotify/me" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Spotify refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Spotify access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Spotify access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "spotify",
    "services": [
      "spotify"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "spotify",    "services": [      "spotify"    ],    "reconnectUrl": "https://…"  }}