---
title: "Create an Agent Copilot Configuration"
method: POST
path: "/v2.0/aicopilotconfigs"
tags: ["Agent Copilot Configuration"]
---

# Create an Agent Copilot Configuration

`POST /v2.0/aicopilotconfigs`

Creates an Agent Copilot configuration in a Project. The Agent Copilot configuration defines the grid layout, which serves as the structure for your AI Copilot Workspace. After creation, select the configuration in the Cognigy.AI Endpoint under the Copilot section.

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Request body

- object
  - `name` string — The human readable name of the config.
  - `description` string — The description which can be used to understand what the agent assist config contains in terms of tiles.
  - `config` object — The actual grid-config.
    - `grid` object
      - `columns` number — Number of columns in the grid.
      - `rows` number — Number of rows in the grid.
      - `gap` number — Padding between tiles in pixels. The default value is 10. If you set it to 0, the default will be used.
    - `tiles` object
      - `tile-id` object — The Tile ID is used in the Flow Nodes to fill in this specific tile.
        - `x` number — The row number where the tile is located, starting from 1.
        - `y` number — The column number where the tile is located, starting from 1.
        - `columns` number — The number of columns the tile should occupy. The default value is 1.
        - `rows` number — The number of rows the tile should occupy. The default value is 1.
  - `projectId` string — The unique identifier for the Project.

## Response `201`

Returns the Agent Copilot Configuration object.

- object — The IEntityMeta defines meta information every entity within the system has. These are dates when a resource was created and modified as well as information about the user who initially created a resource and who modified it the last time.
  - `name` string — The human readable name of the config.
  - `description` string — The description which can be used to understand what the agent assist config contains in terms of tiles.
  - `config` object — The actual grid-config.
    - `grid` object
      - `columns` number — Number of columns in the grid.
      - `rows` number — Number of rows in the grid.
      - `gap` number — Padding between tiles in pixels. The default value is 10. If you set it to 0, the default will be used.
    - `tiles` object
      - `tile-id` object — The Tile ID is used in the Flow Nodes to fill in this specific tile.
        - `x` number — The row number where the tile is located, starting from 1.
        - `y` number — The column number where the tile is located, starting from 1.
        - `columns` number — The number of columns the tile should occupy. The default value is 1.
        - `rows` number — The number of rows the tile should occupy. The default value is 1.
  - `referenceId` string, uuid
  - `_id` string
  - `createdAt` integer — Unix-timestamp
  - `lastChanged` integer — Unix-timestamp
  - `createdBy` string
  - `lastChangedBy` string

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/revisions/85b2872bdfb7/schema)