Skip to content

Analytics · Beta

Pendo
API integration

Ship Analytics features without building the integration. Full Pendo API access via Proxy and 60+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Pendo

Use Cases

Why integrate with Pendo

Common scenarios for SaaS companies building Pendo integrations for their customers.

01

Embed Pendo analytics inside your Customer Success platform

Let your CSM users connect their Pendo account to pull per-account page views, feature usage, and guide engagement into health scores — then push churn risk flags back into Pendo as metadata to trigger targeted in-app guides.

02

Forward AI copilot conversations into Pendo

If you ship an AI assistant or chatbot, let your customers pipe every prompt and response into Pendo as conversation events so their PMs can correlate AI interactions with product behavior natively.

03

Sync external feedback and NPS into your helpdesk or community tool

Push feature requests from your portal into Pendo's feedback module and pull in-app NPS/survey responses back out, giving support and product teams a unified view of user sentiment.

04

Power marketing automation with Pendo segments

Let marketing tools export Pendo visitor segments (e.g. onboarding drop-offs, power users) to trigger email drips, ad retargeting, or lifecycle campaigns against precise in-product cohorts.

05

Automate GDPR/CCPA compliance across Pendo

If you offer a privacy or DSAR workflow tool, let customers trigger Pendo visitor deletions and 'do not process' flags in bulk when end users submit erasure requests.

What You Can Build

Ship these features with Truto + Pendo

Concrete product features your team can ship faster by leveraging Truto’s Pendo integration instead of building from scratch.

01

Two-way metadata sync

Push CRM fields like account tier, renewal date, or health score into Pendo visitor/account metadata in bulk, and pull Pendo usage metrics back into your product.

02

Segment-triggered campaign exports

Let users pick a Pendo segment in your UI, kick off a visitor export, poll for completion, and ingest the resulting CSV of visitor IDs for downstream campaigns.

03

Conversation event capture for AI features

Ship a one-click Pendo connector that streams every AI copilot message — prompt, response, and user context — into Pendo as conversation events.

04

Feedback and feature request forwarding

Create Pendo feedback entries whenever a user submits an idea in your portal, and bulk-update or delete them as statuses change on your side.

05

Cross-object analytics via aggregation search

Expose dashboards that run Pendo's pipeline aggregation queries across pages, features, track events, visitors, and accounts to compute custom metrics in your product.

06

Privacy and deletion automation

Trigger Pendo bulk visitor/account deletions and 'do not process' updates directly from your DSAR or consent management workflow, with status polling for audit logs.

SuperAI

Pendo AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_pendo_page

List all Pendo pages. Returns an array of page records including id, name, appId, kind, createdAt, lastUpdatedAt, group, rules, isCoreEvent, and dirty. Use appId to filter by a single application or expand=* to return pages across all apps in the subscription.

get_single_pendo_page_by_id

Get a single Pendo page by id. Returns a one-element array with the same fields as the list pages tool. Required: id.

list_all_pendo_feature

List all Pendo features. Returns an array of feature records including id, name, appId, kind, isCoreEvent, appWide, elementPathRules, pageId, and 3 more fields. Optionally filter by specific feature IDs with id (comma-separated), scope to one application with appId, or pass expand=* to include all applications in a multi-app subscription.

get_single_pendo_feature_by_id

Get a single Pendo feature by id. Returns a one-element array with the same fields as the list features tool. Required: id.

create_a_pendo_track_event

Send a track event to Pendo to record custom user actions not automatically captured by the browser agent. The endpoint accepts a JSON payload and returns a 200 response on success.

list_all_pendo_track_type

List all track types in Pendo. Returns an array of track type objects including id, name, appId, kind, trackTypeName, trackTypeRules, eventPropertyNameList, isCoreEvent, createdAt, and lastUpdatedAt. Pass expand=* to return track types across all applications in a multi-app subscription.

get_single_pendo_track_type_by_id

Get a single Pendo track type by id. Returns a one-element array with the same fields as the list track types tool. Required: id.

get_single_pendo_visitor_by_id

Get a Pendo visitor by id. Returns the visitor object including id and visitor-specific metadata attributes. Required: id.

list_all_pendo_visitor_history

Get the activity history for a Pendo visitor for a time period beginning at starttime. Returns history event records including id and event-specific attributes. Required: visitor_id, starttime.

get_single_pendo_account_by_id

Get a Pendo account by id. Returns the account object including id and metadata containing auto-captured analytics (firstvisit, lastvisit, lastupdated, idhash), agent-set fields from the installation snippet, and custom metadata fields. Required: id.

list_all_pendo_bulk_deletion

List all outstanding (not yet completed) bulk deletion requests in Pendo. Returns each request's id, ids, kind, createdTime, startedTime, completionTime, stepsComplete, and stepsRemaining.

get_single_pendo_bulk_deletion_by_id

Get the status of a single Pendo bulk deletion request by id. Returns: id, ids, kind, createdTime, startedTime, completionTime, stepsComplete, stepsRemaining, segmentId, statusUrl. Required: id.

create_a_pendo_visitor_bulk_deletion

Submit a bulk deletion request for up to 500 Pendo visitors (GDPR/CCPA). Visitors are queued for deletion and immediately marked Do Not Process so no further data is collected. Returns: id, ids, kind, createdTime, startedTime, completionTime, stepsComplete, stepsRemaining, segmentId, statusUrl. Required: visitors.

create_a_pendo_account_bulk_deletion

Submit a bulk deletion request for up to 500 Pendo accounts (GDPR/CCPA). Accounts are queued for deletion and immediately marked Do Not Process so no further data is collected. Returns: id, ids, kind, createdTime, startedTime, completionTime, stepsComplete, stepsRemaining, segmentId, statusUrl. Required: accounts.

list_all_pendo_segment

List all Pendo segments. Returns: id, name, kind, createdAt, lastUpdatedAt, createdByUser, lastUpdatedByUser, rootVersionId, stableVersionId, isTraining, targetAccount, flagName, shared, createdByApi, definition, pipeline, dependentMetadata, isFocusGroup, segmentId, statusUrl.

get_single_pendo_segment_by_id

Get a single Pendo segment by id. Returns the full segment object including id, name, kind, createdAt, lastUpdatedAt, shared, definition, pipeline, dependentMetadata, and other attributes. Required: id.

update_a_pendo_segment_by_id

Update a Pendo segment by id, replacing its name and visitor list. Returns: segmentId, statusUrl. Required: id.

delete_a_pendo_segment_by_id

Delete an existing Pendo segment by id. Returns: segmentId, statusUrl. Required: id.

get_single_pendo_segment_status_by_id

Get the processing status of a Pendo segment operation. Returns: checkFound, checkTotal, command, entityTagId, entityTagName, lastUpdatedAt, requestId, status, totalTagged, updatePending, warnings, segmentId, statusUrl. Required: segment_id.

create_a_pendo_segment_visitor_export

Start an asynchronous export of the visitors in a Pendo segment. Returns: jobId, statusUrl, segmentId. Use jobId with the status URL to poll for completion. Required: segment_id.

get_single_pendo_segment_visitor_export_by_id

Check the status of a Pendo segment visitor export job. Returns the export status as a plain string (e.g., 'completed'). Required: segment_id, job_id.

list_all_pendo_segment_visitor_export_result

Retrieve the visitor export results for a Pendo segment in CSV format once the export job has completed. Returns a CSV file. Required: segment_id, job_id, content_type.

create_a_pendo_visitor_segment

Create a visitor segment in Pendo by uploading a named list of visitor IDs. Returns: segmentId, statusUrl. Required: name, visitors.

create_a_pendo_account_segment

Create an account segment in Pendo by uploading a named list of account IDs. Returns: segmentId, statusUrl. Required: name, accounts.

create_a_pendo_segment_visitor

Add a single visitor to a Pendo segment. Returns: segmentId, statusUrl. Required: segment_id, visitor_id. Only works for segments created via the API.

delete_a_pendo_segment_visitor_by_id

Remove a single visitor from a Pendo segment. Returns: segmentId, statusUrl. Required: segment_id, id. Only works for segments created via the API.

pendo_segment_visitor_bulk_update

Add or remove small batches of visitors from a Pendo segment in a single call. Returns: multistatus, segmentId, statusUrl. Required: segment_id, patch. Max 10 operations and 1000 visitors per call; only works for segments created via the API.

list_all_pendo_report

List all public reports in a Pendo subscription. Returns: id, name, kind, createdAt, createdByUser, lastUpdatedAt, lastUpdatedByUser, rootVersionId, stableVersionId, ownedByUser, shared, definition, aggregation, segmentId, statusUrl.

list_all_pendo_report_result

Get the results of a Pendo report as a list of JSON objects. The field structure of each row depends on the report's definition and selected columns. Paths, Funnels, Retention, and Data Explorer reports are not supported. Required: report_id.

pendo_report_result_list_csv

Get the results of a Pendo report as CSV text. The column structure depends entirely on the report's definition and selected columns; the response body is not JSON. Paths, Funnels, Retention, and Data Explorer reports are not supported. Required: report_id.

list_all_pendo_guide

List all Pendo guides. Returns guide objects including id, name, state, launchMethod, isMultiStep, steps, and 3 more fields. Optional: appId (filter by application), id (filter by specific guide ID(s), comma-separated), summarizeContent (return condensed fields: guideId, guideName, guideDescription, guideContent, guidePermalink, appIds, status).

pendo_guide_reset

Reset an individual staged Pendo guide by guide_id. All visitors who previously saw the guide become eligible to see it again, and all prior guide data including poll responses will be deleted. Returns a 200 response on success. Required: guide_id.

pendo_guide_bulk_reset

Reset all staged guides in Pendo, reverting every staged guide back to its published state. Returns: guidesReset, segmentId, statusUrl.

get_single_pendo_guide_by_id

Get a single Pendo guide by id. Returns a one-element array with the same fields as the list guides tool. Required: id.

list_all_pendo_guide_history

Retrieve the change history for a specific Pendo guide. Returns: id, attributes, segmentId, statusUrl. Required: guide_id.

pendo_guide_visitor_reset

Reset the record of a specific visitor having seen a specific Pendo guide, making the visitor eligible to see the guide again as if for the first time. Returns a 200 response on success. Required: guide_id, visitor_id.

pendo_visitor_guide_reset

Reset the seen record for all Pendo guides for a specific visitor, making the visitor eligible to see every guide again. Returns a 200 response on success. Required: visitor_id.

create_a_pendo_guide_experiment_export

Export all A/B experiment results for a single Pendo guide. The response is returned as a CSV file download. Required: guide_id.

list_all_pendo_guide_localization

Bulk export XLIFF 1.2 localization data for up to 15 Pendo guides. Returns XLIFF XML containing each guide's translation content. Required: guideids. Max 15 guides per request; any invalid guide ID causes the entire request to fail.

create_a_pendo_guide_localization

Bulk import XLIFF localization data for up to 15 Pendo guide/locale combinations. The body is a JSON object keyed by guide ID, where each value is an object keyed by locale code (e.g., "es") containing translation status data. Returns a localization status map keyed by guide ID and locale code with per-step translation details. Only P2/Visual…

list_all_pendo_guide_order

Get the ordering of guides as configured on the Guides overview Ordering tab in Pendo. Returns: createdByUser, createdAt, lastUpdatedByUser, lastUpdatedAt, appId, guideIds, segmentId, statusUrl.

pendo_guide_segment_bulk_update

Change the audience segment assigned to a specific Pendo guide. Submits a new segmentId to replace the guide's current segment targeting. Returns an empty response on success. Required: guide_id, segmentId.

pendo_guide_state_bulk_update

Change the state of a specific Pendo guide. Allowed values are public, staged, disabled, and draft. Returns an empty response on success. Required: guide_id, state.

list_all_pendo_survey_response

List Pendo survey responses for a given survey over an optional date range, along with a survey-level summary. Returns a survey object (id, name, type, overallScore, responseCount, sentimentCounts), an array of individual responses, and hasMore. Required: survey_id. Max date range span is 180 days.

list_all_pendo_metadata_field

Get the Pendo metadata schema for a given kind (visitor or account). Returns all field group definitions across agent (snippet-passed), auto (auto-captured), custom (manually added), and pendo (Pendo-specific) groups; each field entry includes Type, DisplayName, ElementType, ElementFormat, isHidden, isDeleted, isCalculated, isPerApp, neverIndex,…

create_a_pendo_metadata_field

Create or undelete one or more Pendo metadata fields for visitors or accounts. Accepts an array of field definitions each with name, displayname, and type. Returns a results array with per-field schema and status (created, undeleted, or failed) and a summary with created, failed, total, and undeleted counts. Required: kind, group.

delete_a_pendo_metadata_field_by_id

Delete an existing Pendo metadata field from the schema for a visitor or account. Returns an empty 204 response on success. Required: kind, group, field.

get_single_pendo_metadata_value_by_id

Get the current value of a specific metadata field for a single visitor or account in Pendo. Returns the field value; the shape is field-type-specific (string, number, boolean, time, or list) and cannot be enumerated statically. Required: kind, group, value_id, id (the field name).

pendo_metadata_value_bulk_update

Bulk-set agent or custom metadata field values for multiple visitors or accounts in Pendo in a single call. Returns: total, updated, failed, missing, kind, segmentId, statusUrl. Required: kind, group.

update_a_pendo_metadata_value_by_id

Set the value of a single agent or custom metadata field on a visitor or account in Pendo. If the custom field name does not match an existing field, a new field will be created. Returns an empty 204 response on success. Required: kind, group, value_id, id (the field name).

pendo_guide_opt_out_bulk_update

Opt a visitor or account out of all guide display in Pendo by setting the blacklistguides pendo metadata field. Returns an empty 204 response on success. Required: kind, value_id.

pendo_do_not_process_bulk_update

Set the 'do not process' flag for a Pendo visitor or account, opting them out of all analytics and guide display. Send the JSON boolean `true` as the request body to enable the flag. Returns an empty 204 response on success. Required: kind, value_id.

list_all_pendo_metadata_dependency

Get dependencies for all Pendo metadata fields. Returns a map keyed by field path (kind/group/field), where each entry lists the guides, reports, segments, usedByUnsharedReports and usedByUnsharedSegments that use the field.

get_single_pendo_metadata_dependency_by_id

Get dependencies for a specific Pendo metadata field. Returns the guides, reports, segments, usedByUnsharedReports, and usedByUnsharedSegments tied to the field. Required: kind, group, id (the field name).

list_all_pendo_exclude_list

List all entries in the Pendo exclude list (blacklist), covering all entry types. Returns each entry's id, name (the glob pattern or exact value being excluded), and type (the category of exclusion, e.g., serverGlob, visitorId, ip).

list_all_pendo_exclude_list_type

List Pendo exclude list entries filtered to a specific entry type such as serverGlob, ip, accountId, or visitorId. Returns: id, name, segmentId, statusUrl. Required: type.

list_all_pendo_server

List all server names recorded by Pendo over the life of the subscription. Returns: id, name, flags, lastUpdatedAt, segmentId, statusUrl.

get_single_pendo_server_by_id

Get a single Pendo server record by id (server hostname). Returns: id, name, flags, lastUpdatedAt, segmentId, statusUrl. Required: id.

list_all_pendo_server_flag

Get all Pendo servers matching a specific flag — either blacklisted (excluded from analytics) or staging. Returns: id, name, flags, lastUpdatedAt, segmentId, statusUrl. Required: flagname.

pendo_datasync_gcs_credential_bulk_update

Rotate the service account and secret key for a Google Cloud Storage (GCS) Data Sync destination that has previously been configured in Pendo. Returns a 200 response on successful credential rotation. Required: serviceAccount, secretKey.

pendo_datasync_s_3_credential_bulk_update

Rotate the access key credentials for an Amazon S3 Data Sync destination that has previously been configured in Pendo. Returns a 200 response on successful credential rotation. Required: accessKeyId, secretAccessKey.

pendo_datasync_azure_credential_bulk_update

Rotate the client credentials for a Microsoft Azure Data Sync destination that has previously been configured in Pendo. Returns a 200 response on successful credential rotation. Required: clientId, clientSecret.

list_all_pendo_feedback_option

Get available feedback options from Pendo, including pre-defined labels, apps, product areas, importance levels, idea statuses, and feedback statuses. Returns: labels, apps, productAreas, importance, ideaStatuses, feedbackStatuses, segmentId, statusUrl.

create_a_pendo_feedback

Create a new feedback item in Pendo. Returns: id, accountId, visitorId, title, description, appIds, labels, importance, status, productAreas, linksData, createdById, createdAt, lastUpdatedById, lastUpdatedAt, segmentId, statusUrl. Required: accountId, title, appIds, importance.

update_a_pendo_feedback_by_id

Update an existing feedback item in Pendo by id. Returns: id, accountId, visitorId, title, description, appIds, labels, importance, status, productAreas, linksData, createdById, createdAt, lastUpdatedById, lastUpdatedAt, segmentId, statusUrl. Required: id, appIds.

pendo_feedback_bulk_delete

Delete up to 10 Pendo feedback items by their IDs. Returns an empty 204 response on success. Required: ids. Maximum 10 IDs per request.

create_a_pendo_conversation_event

Send a conversation event to Pendo's Conversations API to capture AI agent interactions from any environment, including mobile apps, browser extensions, and non-web contexts. Returns an empty 200 OK response on success. Required: type, visitorId, timestamp, and props (containing agentId, conversationId, messageId, and content).

pendo_token_verify

Verify a Pendo integration key, confirming whether it is valid and whether it carries write access. Returns: valid, writeAccess, segmentId, statusUrl.

pendo_aggregation_search

Execute a Pendo aggregation query using a MongoDB-like pipeline language to retrieve and transform visitor, account, page, feature, guide, or track event data. Returns: results, segmentId, statusUrl. Required: response, request.

Why Truto

Why use Truto’s MCP server for Pendo

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1100+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Start with Pendo in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s Pendo account

Use Truto’s frontend SDK to connect your customer’s Pendo account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Pendo

Truto’s Proxy API is a 1-to-1 mapping of the Pendo API. You call us, we call Pendo, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Pendo’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Pendo on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication to Pendo work?

Pendo uses integration keys (API keys) scoped to a subscription, which your end user generates in Pendo's settings. Truto handles secure storage, token verification, and injection on every request so you never touch credentials directly.

Can we send server-side or AI events into Pendo?

Yes. Truto supports Pendo's Track Event and Conversation Event endpoints, so you can forward backend events, transactional data, and AI copilot interactions in addition to browser-captured analytics.

How do segment exports work since they're asynchronous?

You create a segment visitor export, Pendo processes it in the background, and you poll the export status until results are ready. Truto exposes the create, status, and result-listing endpoints so you can orchestrate the full flow.

Can we bulk update custom metadata for CRM-style integrations?

Yes. The metadata value bulk update endpoint is supported, which is the standard way to sync account tier, renewal dates, health scores, or any custom fields from your product into Pendo at scale.

Does this cover GDPR / CCPA workflows?

Yes. You can trigger bulk visitor and account deletions, apply 'do not process' flags, and track bulk deletion status — enough to automate DSAR and erasure workflows end-to-end.

How fresh is the data we pull from Pendo?

Reads hit Pendo's API in real time, so freshness matches whatever Pendo itself exposes (aggregated analytics typically have Pendo's own processing lag of a few minutes to an hour depending on the object). There is no additional caching layer in Truto by default.

What if we need a Pendo endpoint that isn't listed?

Truto adds endpoints on request. If your use case needs a resource not currently in the inventory, we can scope and ship it as part of onboarding.

Pendo

Get Pendo integrated into your app

Our team understands what it takes to make a Pendo integration successful. A short, crisp 30 minute call with folks who understand the problem.