canonical: https://jentic.com/apis/pendo.io/pendo-feedback-api # Pendo Feedback API The Pendo Feedback API (formerly Receptive) enables programmatic access to product feedback management, including feature requests, user accounts, voting, and webhook subscriptions. It provides 31 endpoints for querying and managing features, accounts, users, comments, tags, and votes. The API supports both query parameter and header-based API key authentication and is designed for teams collecting structured product feedback at scale. ## For AI agents Query and manage product feedback data including feature requests, user votes, account tags, and webhook subscriptions. Search features and manage user records for feedback collection. ## Scope Does not handle in-app analytics, user guides, or session replay - use for product feedback collection and feature request management only. ## Capabilities - Search and filter feature requests across accounts and priority tags - Track and update user votes on product feature proposals - Manage account records with custom tags for feedback segmentation - Subscribe to webhook events for real-time feedback notifications - Invite end users and vendor team members to the feedback portal - Query comments attached to feature requests for sentiment analysis ## Use cases ### Feature Request Prioritization Aggregate and prioritize feature requests by querying votes, account tags, and comment sentiment. The Pendo Feedback API provides search and filtering across features, enabling product teams to rank requests by customer segment, vote count, or strategic tag. Agents can pull all features, cross-reference with account data, and produce ranked priority lists. Example prompt: Search features via GET /search with a keyword filter, then retrieve vote counts via GET /votes for the top 10 results to produce a ranked priority list ### Customer Feedback Segmentation Segment feedback by account using custom tags to understand which customer cohorts request specific features. The API supports tagging accounts and features independently, enabling cross-referencing between customer segments and their feature priorities. This powers targeted product roadmap decisions for enterprise vs SMB customers. Example prompt: Retrieve all accounts via GET /accounts, apply a custom tag via POST /accounts/{id}/tags for enterprise accounts, then query features filtered by that segment ### Real-Time Feedback Event Processing Subscribe to webhook events for new votes, feature status changes, or comment additions. The API provides POST /hooks for subscription and POST /hooks/unsubscribe for cleanup. Agents can set up event-driven pipelines that trigger Slack notifications, update project management tools, or recalculate priority scores when feedback changes. Example prompt: Create a webhook subscription via POST /hooks with a callback URL and event type for new votes, then verify the subscription is active ### AI Agent Feedback Management via Jentic AI agents discover and execute Pendo Feedback operations through Jentic to manage product feedback without manual API integration. Agents search for feedback capabilities by intent, receive operation schemas, and execute feature searches or vote retrievals through Jentic's unified interface. This reduces integration time from days to under an hour. Example prompt: Search Jentic for 'search product feature requests', load the GET /search operation schema, and execute with a keyword query parameter ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /features | Query all feature requests | | GET | /features/{id} | Get a feature by ID | | GET | /search | Search features by keyword | | GET | /accounts | Query all accounts | | GET | /votes | Get votes on features | | POST | /hooks | Subscribe to webhook events | | GET | /users | Fetch user records | ## Key resources - **Features** — Query, retrieve, and tag feature requests - **Accounts** — Manage customer accounts with custom tags - **Users** — Create, search, invite, and manage user records - **Votes** — Retrieve and update feature votes - **Comments** — Fetch comment records on features - **Hooks** — Subscribe and unsubscribe from webhook events ## Why Jentic - **Setup:** Wiring Pendo Feedback by hand means passing the auth-token as a header or query parameter, targeting the EU feedback host, and paging through features, votes, and accounts yourself. Through Jentic you install once, import the Pendo Feedback API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Pendo Feedback puts the feature id in the URL path (/features/{id}), so a rule can pin your agent to reading a specific feature. You choose the operations it may call, so registering a webhook via /hooks is included only if you add it and search-and-read can stand alone. - **Credential handling:** Your Pendo Feedback auth-token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search product feature requests', and Jentic returns the matching Pendo Feedback operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Pendo Feedback API (alternate slug)** — Same Pendo Feedback API available under an alternate catalog entry. - **Canny API** — Canny focuses on public-facing feature request boards with voting and changelogs. - **UserVoice API** — UserVoice provides enterprise feedback management with NLP-powered insight extraction. - **Typeform API** — Typeform handles survey and form creation that can feed structured feedback into Pendo. ## FAQ ### What authentication does the Pendo Feedback API use? The Pendo Feedback API uses an API key that can be passed either as a query parameter named auth-token or as a request header named auth-token. Generate your key at https://feedback.pendo.io/app/#/vendor/settings?section=integrate. Through Jentic, this key is stored encrypted and agents receive scoped access without handling the raw token. ### Can I search for feature requests by keyword with the Pendo Feedback API? Yes. The GET /search endpoint accepts query parameters to filter feature requests by keyword. Additionally, GET /features returns all features with optional filtering. Both endpoints support pagination for large result sets. ### What are the rate limits for the Pendo Feedback API? The API specification does not document explicit rate limits. The API uses standard HTTP status codes, so monitor for 429 Too Many Requests responses and implement exponential backoff. Contact Pendo support for account-specific rate limit details. ### How do I set up webhooks for feedback events through Jentic? Search Jentic for 'subscribe to feedback webhooks', load the POST /hooks operation schema, and execute with your callback URL and desired event types. The schema includes required fields for subscription configuration. To remove a subscription, use POST /hooks/unsubscribe. ### Can I manage user invitations through the Pendo Feedback API? Yes. POST /users/invite_end_user invites a customer to the feedback portal, and POST /users/invite_vendor_user invites an internal team member. Both endpoints require the user's email and relevant account details. ### How do I tag accounts for feedback segmentation? Use POST /accounts/{id}/tags to overwrite the custom tags on an account. Retrieve existing tags via GET /accounts/{id}/tags. Tags enable filtering features and votes by customer segment for prioritization workflows. ### Can I limit what my agent is allowed to do with the Pendo Feedback API? Yes. Because you run Jentic One yourself, your own rules decide which Pendo Feedback operations and which stored auth-token the agent may use. Pendo Feedback puts the feature id in the URL path at /features/{id}, so a rule can pin the agent to reading one specific feature, and you can keep it to search-and-read via GET /search and GET /features while withholding writes. Registering a webhook through POST /hooks or tagging accounts via POST /accounts/{id}/tags is available to the agent only if you explicitly allow those operations.