SoundCloud | Operate As Docs

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

Website: soundcloud.com
Connects by: Signing in with SoundCloud
Category: Social and video
Services: 1
Tools: 50

Service	Key	Base URL
SoundCloud	`soundcloud`	`https://api.soundcloud.com`

Connecting

Your client presses Connect on their link and approves on SoundCloud'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": [
      "soundcloud"
    ]
  }
]

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

Permissions

What the client reads	Permission it asks for
See your profile and upload and change your tracks	Chosen on the provider's screen

Tools

Install SoundCloud's typed package for your language:

pip install operate-as-soundcloud

pip install operate-as-soundcloud

Run soundcloud.delete_likes_playlists_playlist_id

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

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

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

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.soundcloud.com. 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-.../soundcloud/me" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../soundcloud/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 SoundCloud 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 SoundCloud access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's SoundCloud 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": "soundcloud",
    "services": [
      "soundcloud"
    ],
    "reconnectUrl": "https://…"
  }
}

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