Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
Your Amplitude project tracks user demographics — country, device, platform, language, and custom properties like plan type or role. You pull the composition endpoint to understand who your users actually are, compare that demographic distribution against your existing Mavera personas, and create or adjust personas so they reflect real product usage instead of assumptions. The result is a persona library calibrated to your actual user base.Architecture
Code
Example Output
Error Handling
Composition API date format
Composition API date format
Amplitude uses
YYYYMMDD format (no dashes) for date parameters. Passing 2026-02-15 instead of 20260215 returns a 400 error.Rate limit: 360 queries/hour
Rate limit: 360 queries/hour
The 360/hour limit is shared across all Dashboard REST API endpoints. Each composition query counts as one. On 429, read the
Retry-After header for the exact wait time in seconds.Empty composition segments
Empty composition segments
If custom user properties aren’t set on most users, composition returns sparse data. Ensure your tracking code sets properties via
identify() calls before relying on composition breakdowns.What’s Next
Amplitude Integration
Back to Amplitude integration overview
Journey Mapping
Map conversion paths from user activity timelines
Personas API
Full reference for POST /api/v1/personas
Mave Agent
Full reference for POST /api/v1/mave/chat