API and data sync

Connect your stack with the customer feedback API

The UserVoice customer feedback API, service hooks, and MCP server move ideas, feedback, and accounts between UserVoice and your apps, warehouse, and AI assistants.

Admin API
Read and write ideas, feedback, users, and accounts for custom syncs and reports.
Idea Collection API
Let signed-in customers post, vote, and rate ideas in your own app.
Service hooks
Send signed notifications when ideas, comments, votes, or statuses change.

What users say on G2

Read all 240+ reviews on G2
Integrations are great with Slack and Salesforce to better measure potential business opportunities with feature requests. It is very customizable with their APIs.
Josue T.
Mid-Market (51-1,000 employees), verified review on G2
CSMs can submit feedback on behalf of a user, so we always have a way to quantify a feature request with the accounts and users that want it.
Taylor J.
User Experience Researcher, Mid-Market, verified review on G2
Three ways in

Three ways to put feedback to work in your stack

Customer requests matter outside UserVoice too: in the warehouse, the CRM, your own app, and the reports leadership reads. Each API covers a different part of that.

Admin API
A REST API for ideas, feedback, comments, status updates, users, accounts, forums, labels, and custom fields. Create, update, merge, and link ideas, or pull everything that changed since your last sync.
Idea Collection API
Build your own feedback experience, including in a mobile app. Signed-in customers list, search, and post ideas, vote, and rate. See in-app feedback for the widget that does this without code.
Service hooks
Get a signed request when a new idea, comment, vote, or status change happens. Limit idea events to the forums you choose, and send them to your endpoint or to Slack.
Outcomes

One source of customer demand, everywhere you report

What changes when customer feedback can move to the systems your company already runs on.
One source of customer demand
Ideas, votes, and the accounts behind them sit next to usage, revenue, and support data, so reports stop living in exported spreadsheets.
Fewer copy-paste handoffs
Status changes, new ideas, and links to engineering work reach the teams that need them without someone retyping updates.
Feedback where customers already are
Your own app or portal collects ideas and votes with the customer's account attached, so every request counts.
How it works

Your first customer feedback API sync in five steps

An admin creates an API key in UserVoice, with a name and optional application and callback URLs. A trusted key gets a token from its key and secret and works as an admin, so keep trusted keys out of browsers and mobile apps. Public apps use the authorization code flow with PKCE, so no secret ships in the app.

Tokens travel as bearer tokens over HTTPS and last 24 hours. Every list is paged, and each response reports the rate limit your plan sets. The API guide walks through a first project.

A typical sync
1
Create a key
Name it and choose whether it's trusted.
2
Get a token
Use key and secret for servers, or PKCE for public apps.
3
Pull what changed
Filter lists by update time and page through up to 100 records at a time.
4
Write back
Create ideas and feedback, update statuses, or link issues.
5
Listen for changes
Turn on service hooks so your system hears about new activity.
By role

Customer feedback API connections every team asks for

Most teams start with one question that a report or another system can't answer yet. These are the connections each team usually asks for.

Product teams
Product ops pulls ideas, votes, and statuses into the BI tool next to usage data, and pushes decisions back as status updates. Product teams keep one source of truth for demand.
Revenue operations
RevOps joins ideas to deals and renewals in the warehouse, using the accounts behind each request. Revenue teams start with the CRM sync and add the API for anything custom.
Engineering
Engineers link ideas to Jira issues or Azure DevOps work items, and build feedback into their own app with the Idea Collection API. See linking feedback to Jira and Azure DevOps.
Customer success
A service hook on status changes tells the account team when an idea their customer asked for moves. Customer success teams follow up the same day.
Data teams
Data engineers sync UserVoice to the warehouse with a scheduled job, or with a third-party tool such as Skyvia. Lists filter by update time, so each run fetches only what changed.
Executive teams
Leaders see customer demand in the dashboards they already read, ranked by the accounts behind it. Executive teams get the view without a new tool to log in to.
Beyond the API

Go beyond the API with MCP and your own AI assistant

Not every connection needs a developer. The UserVoice MCP server lets the AI assistant your company already pays for, such as Claude or ChatGPT, read and update UserVoice in plain language. Add it next to the assistant's other connectors, and one conversation moves information between tools that have no native integration.

  • Admins connect with OAuth, with nothing to install
  • The assistant acts with that admin's own permissions
  • View-only admins can read but not change anything
  • Every change is labeled, so the assistant asks first
  • Answers link to each idea in UserVoice
Explore UserVoice AI and MCP →
Claude answering a question with the UserVoice MCP server, listing ideas ranked by supporting revenue
Example connections

Connections you can build in a single conversation

Each example pairs the UserVoice MCP with a connector your assistant already has. The UserVoice steps are tools the MCP server provides. The MCP playbook has tested prompts.

Call notes to feedback
The assistant reads notes from your call recorder or doc tool, finds the matching ideas, and saves each request with the customer attached.
Add the requests from today's Acme call to the matching ideas.
Ideas to engineering tickets
It reads an idea and its supporters, drafts a ticket in your tracker, and links the idea to the Jira issue or Azure DevOps work item.
Link the bulk edit idea to PROJ-482 and summarize who asked.
Renewal prep from two systems
It pulls an account's open requests and revenue from UserVoice and combines them with notes from your CRM or success tool.
Which open ideas does Acme support, and what's shipped this year?
Compare

Build it, ask for it, or plug it in

Choose by who builds and runs the connection. Many teams use all three.

Way to connect
Who sets it up
Best for
Your developers
Warehouse syncs, custom reports, and back-office tools
Idea Collection API
Your developers
Feedback and voting inside your own app
Service hooks
An admin, plus a receiving endpoint
Real-time alerts when ideas, comments, or statuses change
An admin, in their AI assistant
Ad hoc connections and questions, no code
Native integrations
An admin, no code
An admin
Bringing in ideas, voters, and accounts you already have
Plan for it

Plan your customer feedback API sync

The API gives access; your team owns the connection, schedule, and hosting.

You run the sync
UserVoice doesn't host a warehouse connector. Schedule the job, watch it, and keep its credentials on a server.
Hooks aren't retried
Failed service hook deliveries are logged, not resent. Read the delivery logs and fetch missed changes by update time.
One shared rate limit
All keys and MCP calls share a per-minute limit set by your plan. Lists return up to 100 records a page.
Security

Customer feedback API security, built in

See security and compliance for certifications.

OAuth and PKCE
Bearer tokens over HTTPS, PKCE for public apps.
Signed hooks
Each request carries an HMAC-SHA256 signature.
Public endpoints only
Hooks never post to private network addresses.
Admin permissions
MCP acts as the admin who connected it.
Prebuilt connections

Prefer a connection you don't have to build?

Prefer a connection you don't have to build? Native integrations bring feedback and account context in and send decisions out. Revenue on every request starts with a CRM connection.

CRM and customer success
Salesforce integration logoSalesforceHubSpotGainsight integration logoGainsight (add-on)
Delivery
Jira integration logoJiraAzure DevOps integration logoAzure DevOps
Support and chat
Zendesk integration logoZendeskSlack integration logoSlackMicrosoft Teams integration logoMicrosoft Teams
AI assistants
ClaudeChatGPTCodex
Explore integrations →

Customer feedback API: your questions, answered

Which API should our developers use?

The Admin API for syncs, reports, and back-office tools. The Idea Collection API for collecting feedback from signed-in customers in your own app or site.

How do we keep API access secure?

Store trusted keys only on servers, since they act as an admin. Public apps use the authorization code flow with PKCE, so no secret ships in the app.

Can we sync UserVoice to our data warehouse?

Yes, with a connection your team runs. The developer docs have guides for Stitch and Fivetran, or build your own job with the Admin API.

How do we know a service hook delivery worked?

Each request is signed, and failed deliveries are logged. You can read the delivery logs through the Admin API and fetch missed changes by update time.

How is MCP different from the API?

The API is for applications and data jobs your developers build and run. MCP lets an admin's AI assistant read and update UserVoice in conversation, with that admin's permissions.

Are the API and MCP on every plan?

API and MCP access depend on your plan. Ask during your demo which plan includes what your team needs.

Can the API create ideas for our customers?

Yes. The Admin API and the MCP server can create ideas and add feedback on a customer's behalf, so their words and account stay with the request.

Keep exploring

Go deeper where it matters

Put customer feedback where your data lives

Get a free 30-day trial after your demo, see your own customer feedback in a real account.

Book a demo