Pendo

Pendo provides product analytics (page views, feature usage, user flows) and in-app guidance (tooltips, banners, walkthrough overlays) for SaaS products. Its API exposes account data, visitor behavior, NPS responses, and feature adoption metrics. For agents, the API is useful for: pulling feature adoption data into product reporting pipelines, querying account health indicators (DAU, feature engagement), and managing in-app guide targeting rules programmatically. The Aggregation API enables batch metric queries useful for analytics agents. Enterprise focus; most useful when your product already uses the Pendo SDK. Confidence is docs-derived.

API key auth via X-Pendo-Integration-Key header. Keys are subscription-scoped (full access to the account). No fine-grained per-resource scoping on API keys; keys have broad read access to all account data. Key management via Pendo admin settings. HTTPS enforced. Enterprise plans may support OAuth2 for partner integrations via Pendo's integration network.

engageapi.pendo.io provides the Aggregation API reference; app.pendo.io/api/v1 covers the core API. Pendo's developer documentation is adequate but not as polished as API-first platforms. API reference covers endpoints and schemas. Getting started requires a Pendo subscription and API key. Tutorials focus on integration patterns. Community support via Pendo's customer success team.

REST API at app.pendo.io/api/v1 (core) and engageapi.pendo.io (Aggregation). Core API: accounts, visitors, features (page tracking), and guides management. Aggregation API: POST-based metric queries with filter expressions for time-series data. Response payloads are structured JSON with data arrays and metadata. Pagination via startTime/endTime windows for time-series and page/count for entity lists. Webhook support for guide events.

Standard HTTP status codes with JSON error bodies. 401 for invalid API key, 404 for missing account/visitor, 400 for malformed queries. Aggregation API validation errors include field-level details for filter expression syntax issues. Rate limits documented per subscription tier. Pendo's infrastructure is SaaS; uptime SLA on enterprise plans. Data freshness depends on SDK event ingestion cadence (typically near-real-time).