Remote Config API
GET /v1/config
Section titled “GET /v1/config”Fetch remote configuration values for a game. When a player_id is provided, the response includes segment-specific overrides and experiment variant assignments.
Auth: x-game-api-key header
Without Player ID
Section titled “Without Player ID”Returns the base config for the game (cached for 10 minutes):
curl "https://api.questdata.io/v1/config" \ -H "x-game-api-key: YOUR_API_KEY"Response (200):
{ "max_lives": 3, "difficulty_multiplier": 1.0, "holiday_event": false, "daily_reward_coins": 100}With Player ID
Section titled “With Player ID”Returns config with segment overrides and experiment variants applied:
curl "https://api.questdata.io/v1/config?player_id=player-123" \ -H "x-game-api-key: YOUR_API_KEY"Response (200):
{ "max_lives": 5, "difficulty_multiplier": 1.0, "holiday_event": false, "daily_reward_coins": 200, "_experiments": { "onboarding_flow": "variant_b" }}In this example, the player is in a segment with max_lives and daily_reward_coins overrides, and assigned to variant B of the “onboarding_flow” experiment.
Query Parameters
Section titled “Query Parameters”| Parameter | Type | Description |
|---|---|---|
player_id | string | Player ID for segment/experiment resolution |
Caching
Section titled “Caching”- Without
player_id: Server caches for 600 seconds - With
player_id: Cache headerprivate, max-age=60