Pendo Feedback API

{
  "service_type": "platform",
  "base_url": "https://app.pendo.io",
  "auth_method": "api_key",
  "auth_config": {
    "header": "x-pendo-integration-key",
    "notes": "Pendo uses an integration key for the REST API (Feedback/Listen API and general REST API). Keys are generated per subscription per integration in Pendo settings. Some endpoints (e.g. data syncs) may use different credentials such as cloud storage access or webhook signing secrets."
  },
  "endpoints": [
    {
      "name": "Feedback API (Pendo Listen/Feedback)",
      "path": "/api/v1/feedback",
      "method": "GET",
      "description": "Base for Feedback's API endpoints used to read/create feedback, ideas, votes, and related metadata for building custom integrations.",
      "docs_url": "https://developers.pendo.io/"
    },
    {
      "name": "REST API (analytics/metadata)",
      "path": "/api/v1",
      "method": "GET",
      "description": "Pendo's general REST API base used for aggregations, visitor/account metadata, page/feature data, and reporting.",
      "docs_url": "https://developers.pendo.io/"
    },
    {
      "name": "Metadata endpoints",
      "path": "/api/v1/metadata",
      "method": "GET",
      "description": "Retrieve metadata about visitors, accounts, pages, and features in a subscription."
    },
    {
      "name": "Aggregation endpoints",
      "path": "/api/v1/aggregation",
      "method": "POST",
      "description": "Run aggregation queries against Pendo event data."
    },
    {
      "name": "Webhooks",
      "path": "N/A",
      "method": "POST",
      "description": "Outbound webhook delivery of events (e.g. guide events, feedback events) to configured endpoints. Available as an add-on integration."
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "Pendo is sold as a subscription/enterprise SaaS platform. Pricing is quote-based and depends on modules (Product Analytics, Guides, Session Replay, Listen/Feedback, Predict, Agent Analytics, etc.) and MAU/event volume. No public self-serve pricing tiers. Some integrations (Salesforce, API access, webhooks, Twilio Segment) are add-ons.",
      "free_tier": false,
      "free_trial": "Typically available on request"
    }
  },
  "rate_limits": {
    "notes": "Pendo does not publicly document fixed numeric rate limits. Practical limits are governed by subscription contract, event volume, and API usage terms. Integration key scopes determine which endpoints a caller may access. Consult Pendo developer docs / account team for specific limits."
  },
  "capabilities": [
    "REST API for Feedback (Pendo Listen) integrations",
    "REST API for product analytics data (visitors, accounts, pages, features)",
    "Aggregation query API for event data",
    "Metadata retrieval for visitors, accounts, pages, features",
    "Webhooks for event delivery (add-on)",
    "Data Sync export to Snowflake (direct), Amazon S3, Google Cloud Storage, Azure Storage",
    "MCP Server for connecting Pendo data to Claude, ChatGPT, Cursor, and other MCP-compatible AI tools",
    "Pre-built integrations: Salesforce, HubSpot, Slack, Twilio Segment",
    "Predictions push to Salesforce, HubSpot, Slack, and Pendo segments",
    "Native iOS and Android SDK-level data collection (analytics + guides)",
    "Session Replay with client-side privacy controls",
    "In-app Guides, NPS/CSAT/PMF surveys, Orchestrate journeys",
    "Agent Analytics for AI agents and conversational interfaces",
    "Leo conversational AI interface and AI-powered insights"
  ],
  "raw_analysis": "Pendo is a mature, AI-powered product experience platform (14,000+ teams, 40T+ events collected, 1B+ users) combining product analytics, agent analytics, in-app guides, session replay, feedback/Listen, sentiment/NPS, Predict churn modeling, Orchestrate journeys, Data Sync, and an MCP server. It targets product, growth, customer success, and IT teams, with a dedicated digital adoption offering (Pendo for Employees) for third-party enterprise apps via browser extension. From a developer/API standpoint: Pendo exposes documented REST APIs under https://app.pendo.io (developer docs at developers.pendo.io), notably the Feedback (Listen) API described in the provided snippet, plus general REST endpoints for metadata and aggregation and webhook support. Authentication is via per-integration API keys (integration key header) rather than OAuth; some integrations are sold as add-ons (Salesforce, API access, webhooks, Twilio Segment). There is no public self-serve pricing — it is a quote-based enterprise subscription, so free tier is not available (trials on request). Rate limits are not publicly documented in fixed numeric terms; usage is bound by contract and integration key scopes. Maturity is high: SDKs for web/iOS/Android, data warehouse exports (Snowflake/S3/GCS/Azure), an MCP server for AI tooling, and broad third-party integrations. Because the exact API surface (paths, pagination, field sc

3/3 tests passed

{
  "overall": 71,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 5.0,
    "response_parseability": 8.5,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 4.0,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "enterprise_subscription",
    "free_tier": false,
    "free_trial": "on_request",
    "public_pricing": false,
    "notes": "Quote-based; cost depends on modules and MAU/event volume. Hard for agents to estimate cost or recommend to small teams."
  },
  "issues": [
    "No public/self-serve pricing — agents cannot qualify cost fit or provide a quick estimate for users.",
    "No free tier; trial requires sales contact, blocking immediate signup and first-try success.",
    "Auth/onboarding is enterprise-gated (SSO/sales-led), so an AI agent cannot get a user productive in minutes.",
    "Several key capabilities (Salesforce, API access, webhooks, Segment) are paid add-ons, adding procurement friction.",
    "llms.txt is not actually served — endpoint returns the HTML shell instead of plain-text guidance for AI agents."
  ],
  "recommendations": [
    "Publish a machine-readable pricing summary (even 'starting at' tiers) so agents can qualify fit in one response.",
    "Offer a self-serve sandbox or time-boxed free trial with instant signup to raise first_try_success.",
    "Ship a real /llms.txt with concise capability, auth, and endpoint summaries to boost token efficiency and agent onboarding.",
    "Document public rate limits, quotas, and error codes clearly to improve error_clarity.",
    "Given the existing MCP Server, surface its connection details prominently in docs — this is a strong differentiator for AI-agent-driven adoption."
  ]
}