Meow Wolf · OAuth Scopes
Meow Wolf OAuth Scopes
OAuth 2.0
probed
Meow Wolf 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.
CompanyArtEntertainmentImmersive ExperiencesEventTicketingMuseumsTourismRetailMobile Apps
Scopes: 0
Flows:
Method: probed
Scopes (0)
Meow Wolf 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.
Meow Wolf publishes no scope or permission reference — there is no developer documentation of any kind. Every scope below is read verbatim from scopes_supported in the live OIDC discovery document served by the company's Auth0 custom-domain tenant. They are the stock OpenID Connect identity scopes plus Auth0's per-claim scopes; NONE of them grants access to a Meow Wolf business API, because no such API is published. Descriptions are the standard OIDC Core 1.0 / Auth0 meanings, not vendor-authored text.
Meow Wolf publishes no scope or permission reference — there is no developer documentation of any kind. Every scope below is read verbatim from scopes_supported in the live OIDC discovery document served by the company's Auth0 custom-domain tenant. They are the stock OpenID Connect identity scopes plus Auth0's per-claim scopes; NONE of them grants access to a Meow Wolf business API, because no such API is published. Descriptions are the standard OIDC Core 1.0 / Auth0 meanings, not vendor-authored text.
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.