---
title: "Returns the resolved configuration for one `(accountId, departmentId)` pair. 404 when the brand has no row — deliberately not a 200 carrying `enabled: false`. The caller treats 404 as \"disabled, cache the negative\", which is cheaper and unambiguous. A row that was explicitly switched off does return 200 with `enabled: false`."
method: GET
path: "/api/genai/config"
tags: ["GenAiConfig"]
---

# Returns the resolved configuration for one \`(accountId, departmentId)\` pair. 404 when the brand has no row — deliberately not a 200 carrying \`enabled: false\`. The caller treats 404 as "disabled, cache the negative", which is cheaper and unambiguous. A row that was explicitly switched off does return 200 with \`enabled: false\`.

`GET /api/genai/config`

## Query parameters

- `accountId` integer
- `departmentId` integer

## Response `200`

OK

- GenAiConfigDto — Read DTO for the gen-ai interactive support agent configuration. Returned by both the admin endpoint (`/v1/admin/genai/config`) and the internal endpoint (`/api/genai/config`). Every tuning field here is the EFFECTIVE value, already resolved server-side: the brand's own override, else the brand's copilot row, else the platform default. A consumer never has to know the layering existed, and never has to look anything up of its own. There is no defaults DTO: a brand with no row yields no DTO at all. That is the deliberate divergence from Infoset.Types.Models.Admin.CopilotConfigDto, whose service fabricates one when nothing is persisted — here, "never configured" must stay distinguishable from "configured and off".
  - `accountId` integer
  - `departmentId` integer
  - `enabled` boolean
  - `aiBotId` integer, nullable
  - `maxResponseTokens` integer
  - `idleWarningMinutes` integer
  - `idleCloseMinutes` integer
  - `selectedDeskIds` string[], nullable

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found

---

[API](https://skmtc.dev/infoset/apis/infoset-rest-api.md) · [All operations](https://skmtc.dev/infoset/apis/infoset-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/infoset/infoset-rest-api/revisions/f5bc39a1ac15/schema)
