Amplitude API

Name: Amplitude API API
Brand: Amplitude API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct AnalyticsapiKey11 EndpointsREST

For Agents

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

Quickstart

Get started with Amplitude API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"track user events and query behavioral analytics"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amplitude API API.

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

GET STARTED

Start building with Amplitude API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amplitude API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Amplitude API API for, with concrete tasks.

★ 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.

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.

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.

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.

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.

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

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for amplitude api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Amplitude API keys and secret keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw API keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'query funnel conversion rates') and Jentic returns matching Amplitude operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Amplitude integration: 1-3 days for auth setup, endpoint discovery, and query parameter mapping. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mixpanel API

Mixpanel offers similar event-based product analytics with JQL custom queries and lookup table enrichment

Choose Mixpanel when the project needs JQL custom queries or lookup table enrichment, or when the team already uses Mixpanel

Alternative

PostHog API

PostHog combines product analytics with feature flags and session recording in an open-source platform

Choose PostHog when you need feature flags alongside analytics or require a self-hosted, open-source solution

Complementary

Segment API

Segment collects and routes event data to Amplitude and other analytics destinations

Use Segment when you need to route the same event stream to Amplitude plus other tools like data warehouses or marketing platforms

Alternative

Heap API

Heap auto-captures all interactions without manual instrumentation, compared to Amplitude's explicit event tracking

Choose Heap when the project needs retroactive analytics without pre-defined event tracking instrumentation

FAQs

Specific to using Amplitude API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.