Skip to main content
A Remote Configuration is a named configuration payload that the Qonversion SDK fetches at runtime. Use it to feature-flag experiments, change onboarding copy, tune paywall defaults, or deliver any server-controlled JSON to your app without a new release. Configurations can be segmented by user segment, attached to experiment groups, or pinned to specific users.

​
Key concepts

  • Config ID — Stable identifier referenced by the SDK.
  • Status — draft, active, or paused. Only active configurations are served.
  • Payload mapping — Arbitrary JSON payload returned to the SDK. Managed via a dedicated payload-mapping endpoint so large payloads can be edited independently from metadata.
  • User attachment — POST /v4/remote-configurations/{config_id}/users/{user_id} pins a specific user to this configuration, overriding segment rules.
  • Experiments — Remote configurations can be delivered as an experiment group payload.

​
Available endpoints

MethodEndpointDescriptionStatus
GET/remote-configurationsList remote configurationsNew
POST/remote-configurationsCreate a remote configurationNew
GET/remote-configurations/{config_id}Get a remote configurationNew
PUT/remote-configurations/{config_id}Replace a remote configurationNew
DELETE/remote-configurations/{config_id}Delete a remote configurationNew
PATCH/remote-configurations/{config_id}/statusChange status (draft, active, paused)New
GET/remote-configurations/{config_id}/payload-mappingGet the payload mappingNew
POST/remote-configurations/{config_id}/payload-mappingSet the payload mappingNew
POST/remote-configurations/{config_id}/users/{user_id}Attach a user to this configurationNew
DELETE/remote-configurations/{config_id}/users/{user_id}Detach a userNew

​
Authentication

All v4 endpoints require a Secret Key. See Authentication.
These endpoints are live in the api-gateway and the Qonversion MCP server. OpenAPI playground entries will be added in a follow-up once the upstream OpenAPI source is updated.