Rockbot · OAuth Scopes

Rockbot OAuth Scopes

OAuth 2.0 derived

Rockbot uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://api.rockbot.com/v5/api-clients/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyConsumerMusicDigital SignageAudio MessagingRetail MediaIn-Location MediaMediaEntertainment
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.rockbot.com/v5/api-clients/token
Flows
clientCredentials

Scopes (0)

Rockbot implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-21'
method: derived
source: openapi/rockbot-openapi.yml
schemes:
- name: oauth2
  source: openapi/rockbot-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.rockbot.com/v5/api-clients/token
  description: 'OAuth 2.0 Client Credentials grant. Exchange a CLIENT_ID/CLIENT_SECRET (issued
    by Rockbot support) at the token endpoint for a 24-hour bearer ACCESS_TOKEN, then send it
    as `Authorization: Bearer ACCESS_TOKEN`.'
scopes: []