Pendo API is an umbrella term for the application programming interfaces and developer tools Pendo offers for working with its platform. The main REST API is the Engage API, which lets developers securely access and update Pendo data through HTTPS requests and JSON responses.

The API gives developers more control over how they collect, access, and transfer product data. In 2026, Pendo also introduced the Pendo MCP server, extending that access directly to AI tools like Claude and Cursor without requiring custom API wrappers.

But neither eliminates the underlying costs and operational trade-offs. Data Sync for recurring, large-scale exports is a paid add-on, Aggregation API requests have a five-minute processing limit, and new usage data can take up to 30 minutes to appear in Pendo.

Executive summary

  • Engage API lets developers access and manage different Pendo resources such as guides, segments, and visitor or account metadata.
  • Aggregation API retrieves aggregated product usage data for custom reporting, while Data Sync schedules large-scale exports of event-level data to a data warehouse or cloud storage.
  • Native integrations and webhooks can reduce development work, so check whether Pendo already supports your intended workflow.
  • Pendo is a better fit for engineering-led teams willing to invest in API access and engineering resources to support custom tracking and data pipelines.
  • To handle more day-to-day analytics and adoption work without relying on developers for every change, consider Userpilot, the agentic product adoption platform. Product teams can label events and build in-app experiences, while Lia, our AI agent, analyzes usage and recommends actions.

demo CTA

5 Pendo API use cases: What developers can access, build, and manage

You can use the Engage API to query product usage, sync visitor and account metadata, send custom events, and manage supported in-app guide operations.

For product usage data, Pendo offers two ways to retrieve and export information:

  • Aggregation API: Best for small, targeted queries, such as retrieving product engagement scores, feature usage totals, or specific metrics for custom reporting.
  • Data Sync: Scheduled, one-way exports of individual events with millisecond-level timestamps, delivered to supported data warehouses such as Snowflake and BigQuery or to cloud storage.

Pendo also provides software development kits (SDKs) you can integrate into web and mobile applications to track user interactions and deliver in-app guidance:

  • Web SDK: Uses a client-side JavaScript snippet to capture browser interactions and display in-app guidance in web applications. Developers can also use it to update visitor information and trigger supported guide behavior.
  • Mobile SDK: Enables product analytics and in-app guidance in native and supported cross-platform mobile applications.

Using the Engage API requires an eligible Pendo subscription and an integration key. Pendo also provides a Postman collection with sample requests developers can test before building an integration.

1. Query product engagement

Suppose you want to flag accounts whose feature usage has sharply declined over the past 30 days. But Pendo’s built-in reports and dashboards can’t dynamically cross-reference or structure this specific decline against your financial health metrics.

Use the Aggregation API to query the relevant product usage metrics per account. You can then export the JSON results into your business intelligence (BI) tool and blend them with CRM data to surface accounts at high risk of churning.

Example curl request and 200 OK JSON response for Pendo’s “Return a Specific Page” API endpoint

Meanwhile, use Data Sync to answer complex lifecycle questions like “How does feature adoption change among customers who onboarded in Q1 vs Q3?”

After sending timestamped user events to Snowflake or BigQuery, run advanced SQL queries to compare monthly customer cohorts. This can reveal whether newer customers are adopting key features as quickly as earlier cohorts, helping your team spot potential onboarding gaps.

2. Sync user metadata

Pendo can’t automatically collect every customer attribute your team needs for user segmentation. Information such as plan tier or lifecycle stage may live in your CRM.

Engage API lets you sync these attributes to Pendo as visitor or account metadata. This allows your product team to instantly build granular segments, such as “Enterprise Users in the Onboarding Stage,” to deliver highly personalized in-app guidance.

On the engineering side, this introduces challenges that should be actively managed. Users might have different IDs across multiple apps, so the same person can appear as two records. Developers also have to handle failed requests and changes to CRM fields when setting up the sync.

⚡ Pro tip: Before building a custom connection, evaluate Pendo’s native Salesforce and HubSpot integrations. Both support two-way synchronization of selected metadata fields, which could eliminate the need for custom developer pipelines.

3. Track server-side events

Pendo’s client-side SDKs automatically capture common in-app interactions, such as page views and feature clicks on web, and screen views and taps in mobile apps. But they might miss important backend behaviors, such as user status changes and business transactions.

Thus, you need to configure server-side Track Events to send backend data to Pendo’s /track endpoint, passing the relevant visitor and account IDs. For example, when your billing system confirms a subscription upgrade, your server triggers a SubscriptionUpgraded event with the new plan as an event property.

Pendo associates the event with the corresponding visitor and account, allowing product managers to build conversion funnels and paths.

Before implementing Track Events, account for two limits:

  • Each Pendo application supports up to 5,000 uniquely named Track Events.
  • Event properties have a default size limit of 25 KB. If exceeded, Pendo discards the entire property map and replaces it with a system-generated error indicator.

4. Manage in-app guides programmatically

When managing multiple in-app guides, the Engage API lets you automate routine updates, such as fetching guide details, changing deployment statuses, and updating target audience segments.

The API also supports two types of guide resets:

  • For an individual visitor: Clear their guide history to make them eligible to see the walkthrough or announcement a second time.
  • For all visitors: Reset a staged guide’s history across your entire user base. However, this also deletes its existing engagement data, including poll responses.

However, the API cannot fully replace Pendo’s UI. It doesn’t provide documented endpoints for creating complete guides or editing their content. Your design or product team must still use the no-code, visual editor to build steps, write copy, and style UI components. Or, they can ask their preferred AI tool to draft guides through the MCP server.

When these guides are used to deliver brief, element-level explanations or highlight product features, Pendo tooltips offer a more focused way to understand their functionality and use cases.

5. Handle data deletion and compliance requests

Pendo’s Engage API lets developers delete visitor and account data to help fulfill privacy requests under regulations such as General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA). You can also use it to remove unwanted test data.

When a customer requests data erasure, you can submit a bulk deletion request using their visitor or account IDs. Each request can include up to 500 visitors or accounts. The full deletion process can take up to 21 days.

Pendo queues the request first and continues collecting data until the deletion job starts. At that point, it marks the affected records as Do Not Process (DNP) to stop further tracking. If you need to stop data collection sooner, enable DNP separately before submitting the deletion request.

Keep in mind that DNP alone doesn’t erase historical records. The separate deletion process handles that data. This is also different from resetting guide history, which removes guide-specific engagement data without erasing a visitor’s entire activity history.

Pendo API pricing, access, and limitations

Pendo’s subscription doesn’t automatically grant API access. Pendo lists API access, Data Sync, and Webhooks as paid add-ons, meaning custom integrations built around these APIs and webhooks are billed separately.

Contact your Pendo account representative to confirm which add-ons your current plan supports and secure specific pricing quotes.

The subscription fee is only part of the expense. Your organization must also dedicate engineering resources to write aggregation queries, keep visitor and account metadata consistent across systems, debug failed requests, and maintain your server-side tracking infrastructure.

Implementation work can become more involved when you’re working across multiple products. As Wes R., a Head of Product at an enterprise company, described in a G2 review:

Implementation across products has been tricky over past 2 years and required regular reconfiguration. Ensuring that visitor ID is the same across products. Knowing when a Pendo app should map to one or many of our product apps. Knowing how to handle a single product that has several URL subdomains has been challenging.

Pendo API operational constraints

Constraint What Pendo documents What your team should plan for
Aggregation API limits Requests have a five-minute processing limit and a 4 GB response-size limit.
  • Break large queries into smaller date ranges.
  • Use Data Sync for recurring, large-scale exports.
Data freshness Event data processes approximately every 15 minutes. New usage data takes up to 30 minutes to appear. API-submitted metadata can appear within seconds.
  • Account for processing delays in reports.
  • Avoid building workflows that require real-time usage data.
API rate limits Too many requests trigger an HTTP 429 error. Pendo doesn’t specify a fixed numerical request quota.
  • Reduce request frequency across pipelines.
  • Implement retry and backoff handling for HTTP 429 errors.
Tracking requirements Pages and Features must be tagged first. Track Events must also be configured before data is available.
  • Complete tagging and event instrumentation.
  • Don’t build queries that depend on unmapped behaviors.

Ultimately, the right setup depends on your data requirements. A monthly feature usage report has very different infrastructure and maintenance needs from a recurring export of millions of events.

Need product analytics without custom API work? Consider Userpilot

The Pendo API is worth considering for engineering-led teams that need specialized analytics queries, server-side event tracking, and automated data workflows. But for product teams focused on driving adoption and deploying in-app experiences without constant reliance on devs, Userpilot offers a more self-serve approach.

Userpilot is the agentic product adoption platform that combines Product Analytics and In-App Engagement. Its Event Autocapture collects client-side interactions like clicks, page views, text inputs, and form submissions. The Visual Labeler lets non-technical product managers click on UI elements and transform them into labeled events without writing a single line of code.

They can then:

  • Map out end-to-end user journeys using funnels, paths, and retention reports to pinpoint exactly where users drop off.
  • Segment users into cohorts based on product activity and customer attributes.
  • Launch targeted experiences, such as contextual onboarding flows, checklists, interactive tooltips, and banners using a visual builder.

Abrar Abutouq, one of our product managers, fixed a drop-off in our email setup flow without a developer ticket:

Within a few hours, I just created a targeting tooltip and showed it to users and highlighted the correct steps for them to make it clear what to do next. That helped a lot on reducing friction and supporting users in real time without involving our dev team.

Lia, our AI agent, extends these workflows. She answers product questions, analyzes usage data, generates dashboards, and surfaces actionable insights on how to improve adoption.

She also recommends next steps and drafts in-app experiences, segments, or surveys. Your team can review and edit the content or design in Userpilot, preview the result, and decide when to publish it.

Comparison of the custom Pendo API path and the self-serve Userpilot path for using product data.

You can also connect HubSpot to sync customer attributes and product engagement data between systems. This lets you personalize in-app experiences using CRM information without building a custom synchronization process.

Userpilot also offers developer tools for more specialized data workflows. Its Real-time HTTP API is available on Growth and Enterprise plans and supports user and company identification, as well as custom event tracking.

Bulk Event Import and Bulk Event Export are included with Enterprise or available as add-ons on Growth. Data Sync is also included with Enterprise and available as a Growth add-on.

Measure feature adoption without an API project, with Userpilot

The team at Doppler, one of our customers, wanted to get data on newly shipped features without waiting on engineering. With Userpilot’s Visual Labeler, Chief Product and Technology Officer Diego Noya could tag events himself 90% of the time:

When we release a new feature, I can tag the event and see the adoption right away. I’d say I’m about 90% self-sufficient. I can track almost all the events I want on my own.

Like Doppler, you can independently find adoption gaps and help users get more value from your product. Book a Userpilot demo to see how much you can improve your product engagement metrics and analytics workflows even without a custom API integration.


Disclaimer: Userpilot strives to provide accurate information to help businesses determine the best solution for their particular needs. Due to the dynamic nature of the industry, the features offered by Userpilot and others often change over time. The statements made in this article are accurate to the best of Userpilot’s knowledge as of its publication/most recent update on November 1, 2026.

demo CTA

FAQ

Is Pendo API access included in every plan?

No, Pendo’s Free plan doesn’t include API access. The API is a paid add-on, and Pendo doesn’t publicly list its price. Contact Pendo to confirm availability and costs for your subscription.

How do you create and manage a Pendo integration key?

A Pendo admin with subscription-level permissions and integration key access can create a key under Settings > Integrations > Integration Keys. Select + Add Integration Key, enter a description, and select Create.

Copy and store the key securely when it’s generated. Pendo only displays it at creation and can’t recover it later. If you lose the key, you’ll need to generate a new one.

Which companies are like Pendo?

Companies considered as Pendo alternatives include Userpilot, the agentic product adoption platform that combines product analytics with in-app engagement; Appcues, which focuses on onboarding and in-app experiences; and WalkMe and Whatfix, which specialize in enterprise digital adoption.

About the author
Kevin O'Sullivan

Kevin O'Sullivan

Head of Product Design

Kevin O'Sullivan, Head of Product Design at Userpilot. Kevin is responsible for leading and growing a high-performing design team and fostering a culture of creativity and innovation. His leadership guides the overall user experience and ensures Userpilot's solutions remain intuitive, attractive, and market-leading.

All posts