---
title: "Three-way preview of a proposed configuration against running tries"
method: POST
path: "/api/v1/campaigns/{campaign_id}/experiments/config-impact"
tags: ["experiments"]
---

# Three-way preview of a proposed configuration against running tries

`POST /api/v1/campaigns/{campaign_id}/experiments/config-impact`

## Request

- Base URL: `https://api.outrival.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.outrival.com/api/v1/campaigns/{campaign_id}/experiments/config-impact`
- Auth: HTTP bearer

Same answer as GET config-impact, with the proposed config in the body.

Use this when the configuration is too large for a query string. The
decision fields on each affected experiment are the product: fold, merge,
or conflict, never a text guess.

## Path parameters

- `campaign_id` string, required

## Request body

- ConfigImpactRequest: The configuration that would be published, for a read-only preview.
  - `new_config` object, nullable: The proposed published configuration
  - `configuration` object, nullable: Alias of new_config, same meaning as the GET query field

## Response `200`

Successful Response

- object

## Other responses

- `400`: Invalid campaign ID format
- `403`: User may not edit this campaign
- `404`: Campaign not found
- `422`: new_config is missing or is not an object

## Changes

- **2026-09-05** `81b8ad74ef2e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/outrival/apis/fastapi/changes/api/v1/campaigns/:campaign_id/experiments/config-impact/post.md)

---

[API](https://skmtc.dev/outrival/apis/fastapi.md) - [All operations](https://skmtc.dev/outrival/apis/fastapi/llms.txt) - [OpenAPI document](https://skmtc.dev/outrival/apis/fastapi/revisions/f27d90300b5e?raw)