canonical: https://jentic.com/apis/amplitude.com/amplitude

# Amplitude API

Jentic publishes the only available OpenAPI specification for Amplitude API, keeping it validated and agent-ready. Ingest user events via HTTP and batch endpoints, query event segmentation, funnels, retention, and revenue analytics, and export raw behavioral data for warehouse analysis. The API supports user search by ID or property, activity history retrieval, cohort listing, and annotation management across web and mobile product analytics projects.

## For AI agents

Ingest behavioral events, query segmentation and funnel reports, look up user activity, and export raw analytics data from Amplitude projects.

## Scope

Does not handle A/B testing, feature flags, or real-time personalization - use for behavioral event tracking and analytics querying only.

## Capabilities

- Ingest individual and batch events with user properties and event metadata via HTTP
- Query event segmentation reports with time-range and property grouping parameters
- Analyze multi-step funnel conversions between defined event sequences
- Measure user retention by configuring first-event and return-event criteria
- Query revenue metrics including LTV, ARPU, and paying user counts over time
- Search for specific users by Amplitude ID or user property and retrieve their event timeline
- Export raw event data for date ranges to feed external data warehouses

## Use cases

### AI Agent Behavioral Analytics Integration

AI agents query Amplitude segmentation, funnel, and retention endpoints to surface behavioral insights programmatically without manual dashboard interaction. Through Jentic, an agent discovers the needed analytics operation by intent, receives the schema with required parameters, and executes queries to return metric summaries directly within automated workflows. Setup takes minutes instead of days of custom integration.

Example prompt: Query the /2/events/segmentation endpoint for the 'purchase' event over the last 14 days grouped by 'platform' and return daily event counts

### Multi-Step Funnel Analysis

Define conversion funnels with ordered event steps and query the funnels endpoint to get step-by-step conversion counts and drop-off rates. Teams use this to measure onboarding completion, purchase flows, and feature adoption paths. The API returns conversion percentages between each step with configurable date ranges and segment filters.

Example prompt: Query the /2/funnels endpoint with events 'app_open', 'search', and 'purchase' for the last 30 days and return the conversion rate at each step

### Revenue and LTV Reporting

Query the revenue endpoint to retrieve paying user counts, total revenue, average revenue per user (ARPU), and lifetime value (LTV) metrics over configurable time periods. This powers automated investor reports, financial dashboards, and revenue forecasting models that need programmatic access to monetization data without manual export.

Example prompt: GET revenue data from the /2/revenue endpoint for the last 90 days and return total revenue, ARPU, and paying user count

### User Lookup and Activity History

Search for specific users by Amplitude ID or custom properties via the usersearch endpoint, then retrieve their complete event timeline via the useractivity endpoint. This enables customer support agents to pull a user's full behavioral history, debug reported issues by examining their event sequence, and identify patterns in churned user behavior.

Example prompt: Search for a user with email 'user@example.com' via /2/usersearch, then retrieve their last 20 events from /2/useractivity

### Raw Data Export Pipeline

Export raw event data for any date range using the export endpoint, which returns zipped JSON files containing every event with all properties, user IDs, and timestamps. Data teams pipe this into Snowflake, BigQuery, or Redshift for cross-platform attribution modeling, custom ML features, or compliance archival outside of Amplitude's retention window.

Example prompt: GET raw event data from the /2/export endpoint for 2026-04-01 to 2026-04-07 and save the zipped response

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /2/httpapi | Send individual events with user and event properties |
| POST | /batch | Batch-upload multiple events in a single request |
| GET | /2/events/segmentation | Query event segmentation reports |
| GET | /2/funnels | Analyze multi-step funnel conversions |
| GET | /2/retention | Query user retention curves |
| GET | /2/revenue | Retrieve revenue, ARPU, and LTV metrics |
| GET | /2/usersearch | Search for users by ID or property |
| GET | /2/export | Export raw event data for a date range |

## Key resources

- **Events** — Ingest events individually or in batch and export raw event data
- **Segmentation** — Query event-based segmentation reports with filters and groupings
- **Funnels** — Define and analyze multi-step conversion funnels
- **Retention** — Measure return rates with configurable first and return events
- **Revenue** — Query revenue metrics including LTV, ARPU, and paying user counts
- **Users** — Search users and retrieve their event activity history
- **Cohorts** — List behavioral cohorts defined in the project
- **Annotations** — Create and retrieve timeline annotations for events

## Why Jentic

- **Setup:** Wiring the Amplitude API by hand means managing separate API keys and secret keys for ingestion versus analytics and batching event payloads correctly yourself. Through Jentic you install once, import Amplitude from the API Directory, store the keys once, and your agent calls it.
- **Permission scoping:** Amplitude carries the project and query targets in the request body and query string rather than resource ids in the path, so scope the agent to the operations it needs, such as the segmentation and funnel queries. You choose the operations it may call, so raw event export is not included unless you add it.
- **Credential handling:** Your Amplitude API key and secret key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'query funnel conversion rates' or 'get event segmentation', and Jentic returns the matching Amplitude operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel API** — Mixpanel offers similar event-based product analytics with JQL custom queries and lookup table enrichment
- **PostHog API** — PostHog combines product analytics with feature flags and session recording in an open-source platform
- **Segment API** — Segment collects and routes event data to Amplitude and other analytics destinations
- **Heap API** — Heap auto-captures all interactions without manual instrumentation, compared to Amplitude's explicit event tracking

## FAQ

### Why is there no official OpenAPI spec for Amplitude API?

Amplitude does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amplitude API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Amplitude API use?

The Amplitude API uses API key authentication passed in the apiKey header. Some endpoints also require a secret key for server-side access. Through Jentic, your API key and secret are stored encrypted in the credential vault and agents receive scoped access without raw keys entering their context.

### Can I query revenue metrics with the Amplitude API?

Yes. The GET /2/revenue endpoint returns total revenue, average revenue per user (ARPU), lifetime value (LTV), and paying user counts for a configurable date range. You can segment by platform, country, or custom user properties.

### What are the rate limits for the Amplitude API?

The HTTP API event ingestion endpoint allows up to 1000 events per second per project. Query endpoints like segmentation and funnels have concurrency limits of around 5 concurrent requests per project on standard plans, with higher limits on enterprise plans.

### How do I query user retention through the Amplitude API via Jentic?

Search Jentic for 'measure user retention amplitude' to discover the /2/retention operation. Load the schema, specify the first_event and return_event parameters along with a date range, and execute. The endpoint returns day-N retention percentages. Install the SDK with pip install jentic to get started.

### Can I look up a specific user's event history?

Yes. First search for the user via GET /2/usersearch with their Amplitude ID or a user property value. Then retrieve their full event timeline via GET /2/useractivity using the returned Amplitude ID. The activity endpoint returns recent events in reverse chronological order.

### How do I batch-upload events to Amplitude?

POST to the /batch endpoint with a JSON body containing an api_key field and an events array. Each event object requires a user_id or device_id, event_type, and optional event_properties and user_properties objects. The batch endpoint accepts up to 2000 events per request.

### Can I limit what my agent is allowed to do with the Amplitude API?

Yes. Because you run Jentic One yourself, your own rules decide which Amplitude operations and credentials the agent may use. Amplitude carries its project and query targets in the request body and query string rather than as resource IDs in the path, so you scope the agent to only the operations it needs, such as the GET /2/events/segmentation and GET /2/funnels queries. Since you choose the operations it may call, the raw GET /2/export endpoint stays off limits unless you explicitly add it.