Skip to main content
Amplitude holds your product’s behavioral intelligence — user composition, activity timelines, cohort comparisons, and revenue metrics. These four jobs pull that data through Mavera’s surfaces (Custom Personas, Mave Agent, Focus Groups) so your personas reflect real demographics, your journey maps are grounded in actual paths, and your pricing decisions are informed by synthetic audience reactions.

​
API Reference Card

DetailValue
Base URLhttps://amplitude.com/api/2
AuthHTTP Basic Auth (API_KEY:SECRET_KEY)
Rate limits10 concurrent requests; 360 queries/hour
Mavera basehttps://app.mavera.io/api/v1
Mavera authAuthorization: Bearer mvra_live_...
All examples use three environment variables: AMPLITUDE_API_KEY, AMPLITUDE_SECRET_KEY, and MAVERA_API_KEY. Python examples use requests with Basic Auth; JavaScript examples use fetch with a Base64-encoded Authorization header.

​
Prerequisites

1

Amplitude project with data

You need an active Amplitude project with at least 30 days of tracked events and user properties. Find your project in Amplitude → Settings → Projects.
2

API credentials

Create API keys in Amplitude → Settings → Projects → your project → General. Copy the API Key and Secret Key.
3

Mavera API key

Get your key from Mavera dashboard.
4

Environment variables

export AMPLITUDE_API_KEY="your-amplitude-api-key"
export AMPLITUDE_SECRET_KEY="your-amplitude-secret-key"
export MAVERA_API_KEY="mvra_live_xxxxx"

​
Jobs

#JobAmplitude DataMavera SurfaceOutput
1User Composition → Persona Calibration/api/2/compositionCustom PersonasDemographics-calibrated persona set
2User Activity Timeline → Journey Mapping/api/2/useractivityMave AgentJourney maps with conversion paths and friction points
3Behavioral Cohort → Focus GroupCohort behavioral dataFocus GroupsExperience difference insights across cohorts
4Revenue Analysis → Pricing Focus GroupRevenue metrics + ARPUFocus GroupsWillingness-to-pay validation with Slider + NPS

​
Rate Limits & Production Notes

Amplitude EndpointLimitStrategy
Dashboard REST APIs (composition, funnels, etc.)360 queries/hour; 10 concurrentQueue queries; respect Retry-After header on 429
User Activity (/api/2/useractivity)Same pool as Dashboard APIs1s delay between user lookups; batch efficiently
Revenue API (/api/2/revenue/day)Same poolCache daily; revenue data rarely needs real-time refresh
Amplitude’s 360 queries/hour limit is shared across all Dashboard REST API endpoints. If you run all 4 jobs sequentially with the sample sizes shown, you’ll use approximately 50 queries. Spread large user-activity sampling across multiple hours.
Production checklist:
ConcernRecommendation
API key rotationRotate API keys quarterly in Amplitude → Settings → Projects. Secret keys cannot be recovered — store them in a secrets manager.
Date formatAmplitude uses YYYYMMDD (no dashes). Passing ISO dates (2026-02-15) returns 400 errors.
EU data residencyIf your Amplitude project is EU-based, use https://analytics.eu.amplitude.com/api/2 instead of https://amplitude.com/api/2.
User Activity volumeEach user lookup returns up to 1,000 events. For users with more, paginate using the offset parameter.
Mavera creditsMonitor at Dashboard. Focus Groups with 3 personas × 5 questions consume more credits than Mave chat calls.
CachingCache composition and revenue data locally — they update daily at most. User activity data is suitable for weekly re-pulls.

​
What’s Next

All Integrations

50+ API integrations with full code

Amplitude API Docs

Official Amplitude Dashboard REST API reference

Personas API

Full reference for POST /api/v1/personas

Focus Groups API

Full reference for POST /api/v1/focus-groups

Mave Agent

Full reference for POST /api/v1/mave/chat