Pendo Feedback API
Browse all Pendo APIs★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey31 EndpointsREST
For 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.
Use for: I need to search for feature requests matching a keyword, List all votes submitted by a specific user, I want to tag an account for priority feedback tracking, Get details about a specific feature request by ID
Not supported: Does not handle in-app analytics, user guides, or session replay — use for product feedback collection and feature request management only.
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.
Install Jentic One Beta
Connect the Pendo Feedback API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pendo Feedback API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Pendo Feedback API.
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
Patterns agents use Pendo Feedback API for, with concrete tasks.
★ 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.
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.
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.
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.
Search Jentic for 'search product feature requests', load the GET /search operation schema, and execute with a keyword query parameter
Key Endpoints
31 endpoints — the pendo feedback api (formerly receptive) enables programmatic access to product feedback management, including feature requests, user accounts, voting, and webhook subscriptions.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pendo Feedback API keys (auth-token header or query parameter) are stored encrypted in the Jentic vault. Agents receive scoped access without the raw API key entering their context.
Intent-based discovery
Agents search by intent (e.g., 'search product feature requests') and Jentic returns matching Pendo Feedback operations with typed schemas, enabling agents to call the correct endpoint without parsing API documentation.
Time to first call
Direct Pendo Feedback integration: 1-3 days for auth, pagination handling, and webhook setup. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Pendo Feedback API (alternate slug)
Same Pendo Feedback API available under an alternate catalog entry.
These are the same API under different catalog slugs. Use either entry — they point to the same service.
FAQs
Specific to using Pendo Feedback API through Jentic.
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.
GET STARTED