HomeDocumentationAPI Reference
Documentation
Start typing to search…

Not a Developer?

Introduction for non-technical users.

If the words REST, endpoints, or JSON are unfamiliar, that’s okay. You don’t need to be a developer to understand why our APIs matter or how to start a conversation with your internal teams.

The UserTesting APIs let your company automatically access human insight data, like session results, scores (QXscores), video links, transcripts, and related metrics. This information can be used inside your organization’s analytics, data warehouse, BI dashboards, or AI workflows.

Why This Matters

Most customers already use tools like Snowflake, BigQuery, Tableau, Power BI, or AI/ML platforms. Our APIs make it possible for your data teams to bring UserTesting data into those environments automatically, instead of downloading CSVs or manually exporting data.

Use cases include:

  • Automated research data pipelines — refresh UX metrics nightly
  • Dashboards that combine QXscores with product/business metrics
  • AI-powered analysis of videos and transcripts
  • Real-time triggers into tools like Slack or Jira
  • Internal reporting built on session-level results

These integrations help your organization operationalize human insights at scale and make those insights more visible and embedded.

What Your Internal Team Will Want to Know

If you’re not the one building this, here’s something straightforward to say internally:

“We want to use the UserTesting Results API to bring test results, session scores (QXscores), and transcripts into our data warehouse/analytics systems. What’s our standard process for ingesting SaaS API data into our stack?”

That prompts the right discussion and connects you with the team who owns this work.

Helpful Questions to Ask Your Team

Ownership

  • Who handles external data integrations?
  • Who manages our data warehouse / data lake?

Destination

  • Where should this data be stored? (e.g., Snowflake, BigQuery, Redshift)
  • Do we put raw JSON into the warehouse, or transform it first?

How It Gets Pulled

  • Do we use ELT/ETL tools (like Fivetran, Airbyte)?
  • Do we write custom scripts (Python, Airflow, etc.)?
  • How often should this run? (hourly, daily?)

Security

  • How do we securely store API credentials?
  • Does this need a security review?

Maintenance

  • Who will monitor the integration?
  • What happens if the API changes?

What the Technical Team Will Actually Use

Your technical team will care about:

  • API docs & endpoints (Results API v2, Legacy API v1)
  • Authentication (OAuth2 with access token)
  • Endpoint capabilities—e.g., retrieving session details, QXscores, video URLs, transcripts
  • Pagination and data modeling for warehouses

Sharing the API documentation link from this portal is usually enough to get conversations started.

Simple Value Statements You Can Use

High-level business value:

“Our survey and interaction test results can be automatically pulled into our analytics stack, so dashboards and AI models can include UX data alongside product and operational metrics.”

For data teams:

“We need to build an automated pipeline that uses the Results API to sync test results, session details, transcripts, and QXscores into our data warehouse.”

Further resources

For "not-so-technical" documentation to learn more about the Results API, checkout the following resources:


Updated 1 day ago