Skip to main content
Update Custom Analysis Category
The group name is part of the key extracted values arrive under. Values land as custom_analysis["Lead QA"]["Lead Temperature"], so renaming a group changes the shape of every future call payload while leaving past calls under the old name.If anything downstream reads that key — a warehouse column, a CRM mapping, a dashboard — rename on both sides together, or create a new group instead.
Vocily’s built-in “Default Analysis” group cannot be renamed or deleted — 409. Its name is an address other readers depend on, and its model deliberately follows the agent’s own. What you can do is edit each value’s extraction description, switch values off, add your own values to it, or detach the whole group from an agent.
Renaming does not re-run analysis. Calls already analysed keep the values and the names they were analysed under.

Authorizations

Authorization
string
header
required

Your API key as a Bearer token, e.g. Authorization: Bearer vk_….

Path Parameters

group_id
string
required

The analysis group's id, from GET /v1/custom-analysis.

Body

application/json
name
string | null

What to call this group. Renaming changes the key values arrive under on every future call, while past calls keep the old name.

Required string length: 1 - 255
description
string | null

Your own note about what the group is for.

model
string | null

Which LLM runs the extraction.

Required string length: 1 - 128
temperature
number | null

Randomness for the extraction.

Required range: 0 <= x <= 2
max_tokens
integer | null

Cap on the extraction response.

Required range: 50 <= x <= 10000
conditions
CustomAnalysisConditions · object | null

When this group runs at all.

Response

The updated group.

id
string
name
string
description
string | null
model
string | null
temperature
number | null
max_tokens
integer | null
conditions
object
is_default
boolean
items
object[]
created_at
string<date-time>
updated_at
string<date-time>