APIs

Programmatic access to Conviva data via the public REST API.

Updated 2026-09-02 api, rest, endpoints, connect

Welcome to Conviva's developer documentation for APIs.

Conviva APIs provide programmatic access to real-time and historical data visualized in the Conviva Pulse web portal. You can use these APIs to build custom dashboards, extract data for warehouse purposes, or ingest data into third-party tools. Conviva APIs can be easily integrated into the applications and provide HTTP response codes to indicate API errors.

VSI APIs

  • Efficient API Usage: batch metrics, group by a dimension, cache settled windows, and back off on HTTP 429 to stay under the rate limits.

  • Metrics v3 API — retrieve historical and real-time metric values by metric name, with optional group-by dimensions, filters, and sorting.

  • Sessions v3 API — retrieve session-level detail data, including per-viewer session diagnostics.

  • Bulk Filters API — create, retrieve, update, and delete filters in bulk to manage large filter sets programmatically.

  • AI Alerts API — retrieve AI-driven alerts, alert diagnostics, and impacted sessions programmatically.

  • Precision Policy API — programmatic control over Precision policies, including activation and reordering.

  • PII Opt-Out API — mark viewer identifiers for opt-out to satisfy privacy requests.

  • Validation Timeline API v1 and v2 — retrieve session validation timeline data for QA and integration testing.

Detailed OpenAPI (Scalar) references for each API are being wired up separately. Until they land, use the linked guide pages above — each covers request/response shapes, examples, and available endpoints.

Access Limits

Access limits are enforced per c3 account. For the current per-endpoint values, see the Rate Limits section of the Metrics V3 API Guide, the single source of truth for Conviva VSI API rate limits. For full contractual limits and rate plans, see the Conviva service description.

Authentication

To access any Conviva APIs, it is required to provide an API key (client-Id and client-secret). Generate the credentials from the Pulse API Management page.

While calling the Flow API, always use the generated client-Id and client-secret.

Do not use Pulse user-based credentials for any API request. Pulse user-based credentials and Conviva API keys are different. Calling any Conviva APIs with Pulse user-based credentials results in unrecognized credentials and authentication failure.
For any questions contact to Conviva Support (support@conviva.com).

Deleted Historical Resource Data

After a resource is deleted from an account, the resource name may still appear in the related dimension tables and other data displays if any sessions with the resource were long sessions that started before the resource deletion.

API Reference

The interactive API reference will render here once OpenAPI specs are added to learning_center_claude_code_public/specs/. The Scalar integration is wired up and ready to consume spec files (YAML or JSON). The plumbing renders a placeholder until specs exist.