Unwrap · OAuth Scopes

Unwrap OAuth Scopes

OAuth 2.0 searched

Unwrap publishes 5 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Unwrap API on a user’s behalf.

Tokens are issued from https://nlp.api.production.unwrap.ai/oauth/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.

CompanyAi AppsCustomer FeedbackCustomer IntelligenceProduct AnalyticsVoice of CustomerNLPGraphQLMCP
Scopes: 5 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://nlp.api.production.unwrap.ai/oauth/authorize
Token URL
https://nlp.api.production.unwrap.ai/oauth/token
Flows
authorizationCodeclientCredentials

Scopes (5)

ScopeDescriptionFlows
team:*:teams:read Read access to teams / views. authorizationCode, clientCredentials
team:*:groups:read Read access to feedback groups. authorizationCode, clientCredentials
team:*:charts:read Read access to charts. authorizationCode, clientCredentials
team:*:filters:read Read access to filters. authorizationCode, clientCredentials
team:*:entries:read Read access to feedback entries. authorizationCode, clientCredentials

Source

OAuth Scopes

unwrap-scopes.yml Raw ↑
generated: '2026-07-21'
method: searched
source: well-known/unwrap-oauth-authorization-server.json
docs: https://docs.unwrap.ai/articles/6412771011-unwrap-mcp
note: >-
  OAuth 2.0 scopes advertised by the Unwrap MCP / NLP API authorization server
  discovery document. Scopes follow a team:<team_id>:<resource>:<action>
  pattern; the wildcard "*" denotes any team the token is authorized for. All
  published scopes are read-only.
schemes:
  - name: oauth2
    source: well-known/unwrap-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://nlp.api.production.unwrap.ai/oauth/authorize
        tokenUrl: https://nlp.api.production.unwrap.ai/oauth/token
      - flow: clientCredentials
        tokenUrl: https://nlp.api.production.unwrap.ai/oauth/token
scopes:
  - scope: team:*:teams:read
    description: Read access to teams / views.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/unwrap-oauth-authorization-server.json]
  - scope: team:*:groups:read
    description: Read access to feedback groups.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/unwrap-oauth-authorization-server.json]
  - scope: team:*:charts:read
    description: Read access to charts.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/unwrap-oauth-authorization-server.json]
  - scope: team:*:filters:read
    description: Read access to filters.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/unwrap-oauth-authorization-server.json]
  - scope: team:*:entries:read
    description: Read access to feedback entries.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/unwrap-oauth-authorization-server.json]

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/unwrap-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.