UserTesting · OAuth Scopes

UserTesting OAuth Scopes

OAuth 2.0 searched

UserTesting publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the UserTesting API on a user’s behalf.

Tokens are issued from https://auth.usertesting.com/oauth2/aus1p3vtd8vtm4Bxv0h8/v1/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.

CompanyUX ResearchUsability TestingHuman InsightCustomer ExperienceSurveysVideoTranscriptsExperience Metrics

Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.usertesting.com/oauth2/aus1p3vtd8vtm4Bxv0h8/v1/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
studies:read	Read access to test/study results (session summaries and details, transcripts, videos, clips, highlight reels, QXscores) across the workspaces the API user belongs to. The only scope the API docs instruct clients to request.	clientCredentials

📄 Provider scope reference: https://developer.usertesting.com/docs/authorization

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: https://developer.usertesting.com/docs/authorization
docs: https://developer.usertesting.com/docs/authorization
description: >-
  OAuth scopes for the UserTesting APIs. The OpenAPI models only the resulting bearer JWT
  (http/bearer), so no scopes are derivable from the spec; this file captures the scope
  surface documented in the Authorization guide and the Okta authorization-server metadata
  saved in well-known/usertesting-oauth-authorization-server.json. The API-specific scope
  surface is a single read scope — the platform's authorization server additionally lists
  standard OIDC scopes that are not used by the Results/Legacy APIs.
schemes:
- name: oauth2ClientCredentials
  source: https://developer.usertesting.com/docs/authorization
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.usertesting.com/oauth2/aus1p3vtd8vtm4Bxv0h8/v1/token
scopes:
- scope: studies:read
  description: >-
    Read access to test/study results (session summaries and details, transcripts, videos,
    clips, highlight reels, QXscores) across the workspaces the API user belongs to. The only
    scope the API docs instruct clients to request.
  flows: [clientCredentials]
  sources: [https://developer.usertesting.com/docs/authorization]
authorization_server_scopes:
  note: >-
    scopes_supported advertised by the Okta authorization server (RFC 8414 metadata); standard
    OIDC scopes, not API data scopes.
  scopes: [openid, profile, email, address, phone, offline_access, device_sso]

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/usertesting-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.

GitHub Google LinkedIn

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