> ## 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. # Set the 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`. ## OpenAPI ````yaml /api-reference/rest-api-v4.yaml post /remote-configurations/{config_id}/payload-mapping openapi: 3.0.3 info: title: Qonversion REST API v4 version: '4.0' description: >- Qonversion REST API v4 follows REST standards. It has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. servers: - url: https://api.qonversion.io/v4 description: Production security: - secretAuth: [] tags: - name: Users description: Retrieve Qonversion users - name: User Properties description: Manage user-level attributes - name: Identities description: Link Qonversion users to your own auth IDs - name: Entitlements description: Entitlement definitions and user grants - name: Purchases description: A user's purchase history - name: Products description: Products configured in the Qonversion dashboard - name: Remote Configurations description: Server-driven configuration payloads and targeting delivered to the SDK - name: Customers description: Aggregated customer records, properties, permissions, and metrics - name: Segments description: Dynamic and system segments of users - name: Experiments description: Paywall and offering A/B experiments - name: Screens description: No-code paywall screens — CRUD, publish, analytics - name: Analytics description: Charts, cards, cohorts, LTV, and insights - name: Exports description: Asynchronous data exports - name: Events description: Event catalog - name: Scheduled Reports description: Recurring reports delivered to external destinations - name: Integrations description: Third-party integrations configuration - name: Automations description: Event-driven automations - name: Project Settings description: Project-level configuration, secret, and store credentials paths: /remote-configurations/{config_id}/payload-mapping: post: tags: - Remote Configurations summary: Set the payload mapping description: >- 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`. operationId: v4SetRemoteConfigurationPayloadMapping parameters: - name: config_id in: path required: true schema: type: string description: Remote configuration identifier. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/V4RemoteConfigurationPayloadMappingRequest' responses: '200': description: Updated payload mapping content: application/json: schema: $ref: '#/components/schemas/V4RemoteConfigurationPayloadMapping' '400': description: Invalid request content: application/json: schema: $ref: '#/components/schemas/V4Error' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/V4Error' '404': description: Remote configuration not found content: application/json: schema: $ref: '#/components/schemas/V4Error' '415': description: Unsupported Content-Type content: application/json: schema: $ref: '#/components/schemas/V4Error' '500': description: Internal error content: application/json: schema: $ref: '#/components/schemas/V4Error' '504': description: Upstream timeout content: application/json: schema: $ref: '#/components/schemas/V4Error' security: - secretAuth: [] components: schemas: V4RemoteConfigurationPayloadMappingRequest: type: object required: - data properties: data: type: object description: > Full replacement mapping of payload key to SDK-side type. Allowed types: `String`, `Number`, `Bool`, `Json`, `Color`, `Products`, `Screens`. additionalProperties: type: string x-extensible-enum: - String - Number - Bool - Json - Color - Products - Screens example: button_color: Color max_items: Number V4RemoteConfigurationPayloadMapping: type: object description: > 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`). required: - object - url - config_id - data properties: object: type: string example: payload_mapping url: type: string example: >- /v4/remote-configurations/82a42dc2-76f6-46c2-b883-846acaf2070a/payload-mapping config_id: type: string example: 82a42dc2-76f6-46c2-b883-846acaf2070a data: type: object description: Flat map of payload key to its SDK-side type. additionalProperties: type: string x-extensible-enum: - String - Number - Bool - Json - Color - Products - Screens example: button_color: Color max_items: Number V4Error: type: object required: - error properties: error: type: object required: - type - code - message properties: type: type: string enum: - request - resource - logical - internal code: type: string description: | Machine-readable snake_case error code. Examples include `invalid_data`, `invalid_request`, `invalid_product_id`, `not_found`, `already_exists`, `offering_already_exists`, `product_not_in_project`, `cannot_set_main_directly`, `cannot_demote_main`, `cannot_patch_experiment_variant`, `cannot_delete_experiment_variant`, and `cannot_setmain_experiment_variant`. Resource-specific codes are documented on the corresponding reference page. message: type: string description: Human-readable description. May change; do not parse. details: type: array nullable: true description: Per-field validation errors, present on 400 validation failures. items: type: object properties: field: type: string message: type: string securitySchemes: secretAuth: type: http scheme: bearer bearerFormat: sk_… description: >- Bearer authentication using the project **Secret Key** (prefixed with `sk_`, or `test_sk_` for sandbox). All v4 public endpoints require the Secret Key — see [Authentication](/reference/v4/authentication). Never expose the Secret Key in client-side code. ````