Type mapping
An extraction returns one value, not a nested structure. Pre-defined options accept
sub_options, but these fold into the same flat set of allowed answers instead of nesting. That is why a multi-part item becomes several extractions in a shared category.
What to do
1
List your configured items and their types
2
Create a category per logical group
For example
Loan Eligibility.3
Add one extraction per item
Use the mapping above. Set name to the existing key to keep result keys stable.
4
For eligibility_analysis, name the verdict
Give the verdict a real name instead of the fixed
eligibility_key.5
Test against a real past transcript
6
Remove the Custom Analytics items from the agent
Before and after
advanced_list and eligibility items were flattened up to the same level as everything else, rather than nested. That structure is unchanged in principle: related fields now sit in a shared category instead.
What changes in your code
Full detail on the result object is in What the payload looks like.
Other features
Extraction
extracted_data · flat keysAgent Extraction
agent_extractionCall Summary
summaryexecution_id for a payload that does not match this guide.
Next Steps
Using Extractions
Configure extractions in the dashboard
Dispositions API
Manage extractions programmatically
Webhooks
Receive extraction data in real-time

