---
title: "Create a Configuration"
method: POST
path: "/v2/ControlPlane/Configurations"
tags: ["ConversationsV2Configuration"]
---

# Create a Configuration

`POST /v2/ControlPlane/Configurations`

Create a new Configuration

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `displayName` string, required — A human-readable name for the configuration. Limited to 32 characters.
  - `description` string, required — Human-readable description for the configuration.
  - `conversationGroupingType` 'GROUP_BY_PROFILE' | 'GROUP_BY_PARTICIPANT_ADDRESSES' | 'GROUP_BY_PARTICIPANT_ADDRESSES_AND_CHANNEL_TYPE', required — Type of Conversation grouping strategy: - `GROUP_BY_PROFILE`: Groups Communications by resolved Profile from the Memory Store. A Profile is looked up or created for `CUSTOMER` Participant types. All Communications from the same Profile are in the same Conversation, regardless of address or channel. - `GROUP_BY_PARTICIPANT_ADDRESSES`: Groups Communications by Participant addresses across all channels. A customer using +18005550100 will be in the same Conversation whether they contact by SMS, WhatsApp, or RCS. - `GROUP_BY_PARTICIPANT_ADDRESSES_AND_CHANNEL_TYPE`: Groups Communications by both Participant addresses AND channel. A customer using +18005550100 by SMS will be in a different Conversation than the same customer by Voice.
  - `memoryStoreId` string, required — The memory store ID that Conversation Orchestrator uses for profile resolution.
  - `channelSettings` object
  - `statusCallbacks` object[] — A list of webhook configurations.
    - `url` string, uri, required — The destination URL for webhooks.
    - `method` 'POST' | 'GET' — The HTTP method used to invoke the webhook URL.
  - `intelligenceConfigurationIds` string[] — A list of Conversational Intelligence configuration IDs.
  - `memoryExtractionEnabled` boolean — Whether memory extraction is enabled for conversations under this configuration. Defaults to false.
  - `conversationsV1Bridge` object — Configuration for Conversations V1 bridge. When set, messaging channels route through Conversations V1. Use this to integrate with existing Conversations V1 applications.
    - `serviceId` string, required — The Conversations V1 Service SID (IS prefix). One configuration per V1 Service SID.

## Response `202`

Accepted - Operation created for asynchronous processing

- object — Slim response for an accepted long-running operation.
  - `statusUrl` string, uri, required — URL to poll for operation status.
  - `related` object, nullable — Named resource identifiers associated with this operation. Keys depend on the operation type: - config-create, config-update, config-delete: configurationId - conversation-delete: conversationId

## Other responses

- `400` — Bad Request
- `409` — Conflict
- `429` — Too Many Requests
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.dev/twilio/apis/conversations-v2.md) · [All operations](https://skmtc.dev/twilio/apis/conversations-v2/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/twilio/conversations-v2/revisions/f039dce07916/schema)