---
title: "Set the payload mapping"
method: POST
path: "/remote-configurations/{config_id}/payload-mapping"
tags: ["Remote Configurations"]
---

# Set the payload mapping

`POST /remote-configurations/{config_id}/payload-mapping`

Replaces the payload **mapping** (key → type schema). Full replace: the supplied `data` object becomes the complete mapping. Allowed types: `String`, `Number`, `Bool`, `Json`, `Color`, `Products`, `Screens`.

## Path parameters

- `config_id` string, required

## Request body

- V4RemoteConfigurationPayloadMappingRequest
  - `data` object, required — Full replacement mapping of payload key to SDK-side type. Allowed types: `String`, `Number`, `Bool`, `Json`, `Color`, `Products`, `Screens`.

## Response `200`

Updated payload mapping

- V4RemoteConfigurationPayloadMapping — The payload **mapping**: the key → type schema describing how the SDK should interpret each payload key. This is the schema — not the delivered values (see `V4RemoteConfigurationPayload`).
  - `object` string, required
  - `url` string, required
  - `config_id` string, required
  - `data` object, required — Flat map of payload key to its SDK-side type.

## Other responses

- `400` — Invalid request
- `401` — Unauthorized
- `404` — Remote configuration not found
- `415` — Unsupported Content-Type
- `500` — Internal error
- `504` — Upstream timeout

---

[API](https://skmtc.net/qonversion/apis/qonversion-rest-api-v4.md) · [All operations](https://skmtc.net/qonversion/apis/qonversion-rest-api-v4/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/qonversion/qonversion-rest-api-v4/versions/e3f72cf8951c/schema)