Ximalaya · OAuth Scopes
Ximalaya OAuth Scopes
OAuth 2.0
searched
Ximalaya 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.
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.
CompanyAudioPodcastsAudiobooksMediaContent DistributionStreamingChinaEntertainment
Scopes: 0
Flows:
Method: searched
Scopes (0)
Ximalaya 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.
Derived by SEARCH, not by derive-oauth-scopes.py: Ximalaya publishes no OpenAPI, so there are no oauth2 securityScheme flows to read. The scope list below is quoted verbatim from the scope string returned in the documented /oauth2/v2/access_token response example.
Derived by SEARCH, not by derive-oauth-scopes.py: Ximalaya publishes no OpenAPI, so there are no oauth2 securityScheme flows to read. The scope list below is quoted verbatim from the scope string returned in the documented /oauth2/v2/access_token response example.
📄 Provider scope reference: https://open.ximalaya.com/doc/detailApi?categoryId=9&articleId=75
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.