Skip to main content

Transitioning from Insight templates to AI fields in Claap's API and Webhooks

Written by Marta Connor

Claap is revisiting how Insights generated for a recording are being made available as AI fields through the interface, the MCP, the API, and webhooks. The newer AI fields will be available in a flatter structure, outside of any grouping.

⚠️ Starting the 15th of June 2026, the recording insightTemplates attribute will no longer be filled and will be replaced by the aiFields attribute. aiFields will contain the recording insights in a flat collection.

Upcoming changes to Claap's API and webhooks

What currently appears as

"insightTemplates": [
{
"templateTitle": "<string>",
"insights": [
{
"langIso2": "<string>",
"sections": [
{
"description": "<string>",
"title": "<string>"
}
]
}
]
}
]

Will now be available as

"aiFields": [
{
"description": "<string>",
"title": "<string>"
}
]

Enabling the new format in your webhooks

Any new webhook created will have the new format by default.

⚠️ To migrate to the new output format before the 15th of June 2026, update your webhook configuration to enable the new aiFields attribute.

You can choose to toggle this ON/OFF for any webhook by adjusting the setting "Include AI fields in the payload" in the Create/Edit popin. To do this:

  1. Go to Settings > API & Webhooks

  2. Click on "..." for the desired webhook

  3. Click on Edit

  4. Adjust the setting to ON or OFF

πŸ’‘ When the setting is ON, the webhook payload will contain the aiFields attribute instead of insightTemplates.

Enabling the new format in your API calls

You can choose the output format in your API response by setting the parameter returnAiFields to either true or false.

πŸ’‘ When returnAiFields in your request is set to true, the API response output will replace the insightTemplates attribute with the new aiFields attribute.

Technical documentation for the new AI fields attribute

Did this answer your question?