---
title: "Get Agent Copilot Configurations"
method: GET
path: "/v2.0/aicopilotconfigs"
tags: ["Agent Copilot Configurations"]
---

# Get Agent Copilot Configurations

`GET /v2.0/aicopilotconfigs`

Gets Agent Copilot configurations for a Project. By default, 25 audit events are returned. Use the `limit` query parameter to change this value.

## Query parameters

- `projectId` string
- `filter` string
- `limit` integer
- `skip` integer
- `sort` string
- `next` string
- `previous` string

## Headers

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

## Response `200`

Returns an array of Agent Copilot configuration objects.

- object
  - `items` 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.
    - `referenceId` string, uuid
    - `_id` string
    - `createdAt` integer — Unix-timestamp
    - `lastChanged` integer — Unix-timestamp
    - `createdBy` string
    - `lastChangedBy` string
  - `total` integer
  - `nextCursor` string
  - `previousCursor` 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/versions/85b2872bdfb7/schema)