> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Remote Configurations

> Server-driven configuration payloads delivered to the SDK

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 `inactive`. 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

| Method | Endpoint                                             | Description                                   | Status |
| ------ | ---------------------------------------------------- | --------------------------------------------- | ------ |
| GET    | `/remote-configurations`                             | List remote configurations                    | New    |
| POST   | `/remote-configurations`                             | Create a remote configuration                 | New    |
| GET    | `/remote-configurations/{config_id}`                 | Get a remote configuration                    | New    |
| PUT    | `/remote-configurations/{config_id}`                 | Replace a remote configuration                | New    |
| DELETE | `/remote-configurations/{config_id}`                 | Delete a remote configuration                 | New    |
| PATCH  | `/remote-configurations/{config_id}/status`          | Change status (`draft`, `active`, `inactive`) | New    |
| GET    | `/remote-configurations/{config_id}/payload-mapping` | Get the payload mapping                       | New    |
| POST   | `/remote-configurations/{config_id}/payload-mapping` | Set the payload mapping                       | New    |
| POST   | `/remote-configurations/{config_id}/users/{user_id}` | Attach a user to this configuration           | New    |
| DELETE | `/remote-configurations/{config_id}/users/{user_id}` | Detach a user                                 | New    |

## Authentication

All v4 endpoints require a **Secret Key**. See [Authentication](/reference/v4/authentication).

<Note>
  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.
</Note>