UserTesting
UserTesting is a human insight platform for experience research: teams recruit vetted participants, run usability tests, surveys, live conversations, and interaction tests, and analyze session videos, transcripts, and QXscore experience metrics. Its developer surface at developer.usertesting.com exposes the Results API (v2) for programmatic access to session data, videos, transcripts, clips, highlight reels, and QXscores, plus Legacy (v1) endpoints for embedding content from classic tests. Authentication is OAuth 2.0 client credentials issued against its Okta authorization server, and an official MCP server (early access) connects the platform to Claude, ChatGPT, Figma Make, and other AI clients.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles UserTesting the way a machine reads it — 15 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — UserTesting scores 59.4/100 (developing), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile UserTesting
Each block below is one kind of artifact we hold for UserTesting. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
UserTesting Clip API
The Clip API from UserTesting — 1 operation(s) for clip.
UserTesting General Session Data API
Retrieve session summaries and detailed session results from a test.
UserTesting Highlightreel API
The Highlightreel API from UserTesting — 1 operation(s) for highlightreel.
UserTesting QXscore Data API
Access Quality of Experience Scores (QXscores) calculated from a test's completed sessions.
UserTesting Session API
The Session API from UserTesting — 1 operation(s) for session.
UserTesting Studies API
The Studies API from UserTesting — 2 operation(s) for studies.
UserTesting Video Data API
Access session video data, including transcripts, video download links, clips, and highlight reels.
UserTesting Workspaces API
The Workspaces API from UserTesting — 2 operation(s) for workspaces.
Scroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
usertesting-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Usertesting Rate Limits
RATE LIMITSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Usertesting Trust Center
SOC 2, ISO 27001:2022 (auditor CoalFire), ISO 27701, CSA STAR, HIPAA, GDPR, CCPA
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for UserTesting — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/usertesting · machine-readable index on apis.io