Changelog
Changes to the partner-facing API, newest first. PlayerPal is in pre-release: endpoints marked In development can still change. Every route stays under /v1.
Partner API reference
The API reference is now generated from the API's own code, with descriptions for every partner endpoint, request and response schemas, and error codes. The OpenAPI 3.1 document is published at /openapi/partner.json.
Insights
GET /v1/kpis/intelligence/insights returns ranked, explainable insights with an executive summary, and GET /v1/kpis/intelligence/insights/{id} returns one insight with its evidence. See Insights.
Explore endpoints for providers
Segments, journey funnel and per-game views were added under /v1/kpis/explore.
Fact ingest
POST /v1/ingest accepts daily fact batches (gameplay, game catalogue, commercial and attribution) with per-record validation and idempotent receipts. See Fact ingest.
KPI API
- Own KPIs, breakdowns by market, game or partner, monthly retention cohorts, the link funnel and previous-period series under
/v1/kpis. - Anonymous network comparison and peer benchmarks, with peer and account thresholds.
- The partner overview at
GET /v1/kpis/overviewlists every KPI with its availability for your feeds.
Partner authentication
Partner routes accept PP-HMAC-SHA256 request signing or OAuth 2.0 client-credentials tokens, with scopes. See Authentication.
Bulk activity uploads
Large activity files can be sent through POST /v1/activity-uploads and completed with a checksum. See Sending activity.
Studio analytics
Game providers can read studio analytics at GET /v1/analytics/studio and per alias.
Activity batches
POST /v1/activity-batches accepts settled rounds for points and analytics, idempotent on batch_id.