Skip to content
Merged
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
5ed3b15
Update API specifications with fern api update
invalid-email-address Jul 2, 2026
01d8b36
Update API specifications with fern api update
invalid-email-address Jul 7, 2026
a2c8645
Update API specifications with fern api update
invalid-email-address Jul 8, 2026
43b4ecf
Update API specifications with fern api update
invalid-email-address Jul 9, 2026
d0979ce
Update API specifications with fern api update
invalid-email-address Jul 14, 2026
5b79eb0
Update API specifications with fern api update
invalid-email-address Jul 15, 2026
f860d70
Update API specifications with fern api update
invalid-email-address Jul 18, 2026
44a8826
Update API specifications with fern api update
invalid-email-address Jul 23, 2026
7e8bea6
Update API specifications with fern api update
invalid-email-address Jul 25, 2026
631ef17
Update API specifications with fern api update
invalid-email-address Jul 30, 2026
8b7450a
Update API specifications with fern api update
invalid-email-address Jul 31, 2026
69e0178
Update API specifications with fern api update
invalid-email-address Aug 6, 2026
5d0bc0a
Update API specifications with fern api update
invalid-email-address Aug 8, 2026
efe0e21
Update API specifications with fern api update
invalid-email-address Aug 12, 2026
b93432a
Merge remote-tracking branch 'origin/main' into resolve-1127
stephenvapiai Aug 12, 2026
d365e35
Update API specifications with fern api update
invalid-email-address Aug 14, 2026
c673239
Merge remote-tracking branch 'origin/main' into resolve-1143
stephenvapiai Aug 14, 2026
b855861
Update API specifications with fern api update
invalid-email-address Aug 16, 2026
e05cb22
Merge branch 'main' into update-openapi-spec
stephenvapiai Aug 17, 2026
0ce623a
Update API specifications with fern api update
invalid-email-address Aug 19, 2026
c7974b4
Merge branch 'main' into update-openapi-spec
stephenvapiai Aug 19, 2026
17af1c8
Update API specifications with fern api update
invalid-email-address Aug 23, 2026
3027eb3
Merge branch 'main' into update-openapi-spec
stephenvapiai Aug 24, 2026
49e54ef
Update API specifications with fern api update
invalid-email-address Aug 26, 2026
74e9a06
Merge branch 'main' into update-openapi-spec
stephenvapiai Aug 26, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions fern/apis/api/openapi.json
Original file line number Diff line number Diff line change
Expand Up @@ -12183,6 +12183,20 @@
"maximum": 3000,
"description": "Maximum delay in milliseconds between when the speaker stops and when the endpoint is detected. Lower values mean faster turn-taking but more false endpoints. Range: 500-3000. Default: 500."
},
"endpointSensitivity": {
"type": "number",
"description": "How likely Soniox is to emit an endpoint (end the caller turn). Higher values make endpoints more likely for faster turn-taking; negative values make them less likely, which helps when callers pause mid-sentence (e.g. reading numbers group by group). Range: -1.0 to 1.0. Default: 0.3 (the platform low-latency voice profile; Soniox's own default is 0.0). Supported by stt-rt-v5; omitted from the Soniox request on explicit stt-rt-v4. Soniox recommends tuning endpointLatencyAdjustmentLevel first, and advises against negative sensitivity while the level is above 0 (the settings work against each other).",
"minimum": -1,
"maximum": 1,
"example": 0.3
},
"endpointLatencyAdjustmentLevel": {
"type": "number",
"description": "How aggressively Soniox reduces endpoint latency. 0 is Soniox's default semantic endpointing; 3 is the most aggressive. Higher levels return endpoints sooner but may split speech into more segments and slightly reduce accuracy. Integer. Range: 0-3. Default: 2 (the platform low-latency voice profile; Soniox's own default is 0). Supported by stt-rt-v5; omitted from the Soniox request on explicit stt-rt-v4.",
"minimum": 0,
"maximum": 3,
"example": 2
},
"customVocabulary": {
"description": "Custom vocabulary terms to boost recognition accuracy. Useful for brand names, product names, and domain-specific terminology. Maps to Soniox context.terms.",
"type": "array",
Expand Down Expand Up @@ -15261,6 +15275,20 @@
"maximum": 3000,
"description": "Maximum delay in milliseconds between when the speaker stops and when the endpoint is detected. Lower values mean faster turn-taking but more false endpoints. Range: 500-3000. Default: 500."
},
"endpointSensitivity": {
"type": "number",
"description": "How likely Soniox is to emit an endpoint (end the caller turn). Higher values make endpoints more likely for faster turn-taking; negative values make them less likely, which helps when callers pause mid-sentence (e.g. reading numbers group by group). Range: -1.0 to 1.0. Default: 0.3 (the platform low-latency voice profile; Soniox's own default is 0.0). Supported by stt-rt-v5; omitted from the Soniox request on explicit stt-rt-v4. Soniox recommends tuning endpointLatencyAdjustmentLevel first, and advises against negative sensitivity while the level is above 0 (the settings work against each other).",
"minimum": -1,
"maximum": 1,
"example": 0.3
},
"endpointLatencyAdjustmentLevel": {
"type": "number",
"description": "How aggressively Soniox reduces endpoint latency. 0 is Soniox's default semantic endpointing; 3 is the most aggressive. Higher levels return endpoints sooner but may split speech into more segments and slightly reduce accuracy. Integer. Range: 0-3. Default: 2 (the platform low-latency voice profile; Soniox's own default is 0). Supported by stt-rt-v5; omitted from the Soniox request on explicit stt-rt-v4.",
"minimum": 0,
"maximum": 3,
"example": 2
},
"customVocabulary": {
"description": "Custom vocabulary terms to boost recognition accuracy. Useful for brand names, product names, and domain-specific terminology. Maps to Soniox context.terms.",
"type": "array",
Expand Down Expand Up @@ -17089,6 +17117,11 @@
"type": "string",
"description": "This is the assistant to transfer the call to."
},
"name": {
"type": "string",
"description": "This is the name of the transfer destination. This is just for your own reference.\n\nUsage:\n- Optional. Stored with the destination wherever it is supplied. For `number`\n and `sip` destinations it is also persisted on the transfer record in the\n call artifact after a transfer and displayed in the dashboard call log (on\n the transfer divider in the transcript view) alongside the destination.\n When omitted, everything behaves exactly as before.\n- Display-only. Unlike `description`, it is never included in prompts or tool\n descriptions and has no effect on model behavior or destination choice.",
"maxLength": 40
},
"description": {
"type": "string",
"description": "This is the description of the destination, used by the AI to choose when and how to transfer the call."
Expand Down Expand Up @@ -18042,6 +18075,11 @@
}
]
},
"name": {
"type": "string",
"description": "This is the name of the transfer destination. This is just for your own reference.\n\nUsage:\n- Optional. Stored with the destination wherever it is supplied. For `number`\n and `sip` destinations it is also persisted on the transfer record in the\n call artifact after a transfer and displayed in the dashboard call log (on\n the transfer divider in the transcript view) alongside the destination.\n When omitted, everything behaves exactly as before.\n- Display-only. Unlike `description`, it is never included in prompts or tool\n descriptions and has no effect on model behavior or destination choice.",
"maxLength": 40
},
"description": {
"type": "string",
"description": "This is the description of the destination, used by the AI to choose when and how to transfer the call."
Expand Down Expand Up @@ -18093,6 +18131,11 @@
"type": "object",
"description": "These are custom headers to be added to SIP refer during transfer call."
},
"name": {
"type": "string",
"description": "This is the name of the transfer destination. This is just for your own reference.\n\nUsage:\n- Optional. Stored with the destination wherever it is supplied. For `number`\n and `sip` destinations it is also persisted on the transfer record in the\n call artifact after a transfer and displayed in the dashboard call log (on\n the transfer divider in the transcript view) alongside the destination.\n When omitted, everything behaves exactly as before.\n- Display-only. Unlike `description`, it is never included in prompts or tool\n descriptions and has no effect on model behavior or destination choice.",
"maxLength": 40
},
"description": {
"type": "string",
"description": "This is the description of the destination, used by the AI to choose when and how to transfer the call."
Expand Down
Loading