Skip to content

Commit f48b9cf

Browse files
fern-api[bot]fern-api[bot]
authored
🌿 ✨ [Scheduled] Update API Spec (#150)
* feat(api): add Gemini Flash 2.0 Multimodal Live API support * feat(openapi): Add new credential types and Azure blob storage * feat(openapi): update OpenAPI spec to support multiple providers for UpdatePhoneNumberDTO * feat(openapi): add new tool types and improve tool configuration * feat(openapi.json): added ClientInboundMessageEndCall object and EndCall action to the ClientInboundMessageTransfer properties. --------- Co-authored-by: fern-api[bot] <115122769+fern-api[bot]@users.noreply.github.com>
1 parent aa5473f commit f48b9cf

File tree

1 file changed

+276
-0
lines changed

1 file changed

+276
-0
lines changed

‎fern/apis/api/openapi.json

Lines changed: 276 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25962,6 +25962,21 @@
2596225962
}
2596325963
}
2596425964
},
25965+
"ClientInboundMessageEndCall": {
25966+
"type": "object",
25967+
"properties": {
25968+
"type": {
25969+
"type": "string",
25970+
"description": "This is the type of the message. Send \"end-call\" message to end the call.",
25971+
"enum": [
25972+
"end-call"
25973+
]
25974+
}
25975+
},
25976+
"required": [
25977+
"type"
25978+
]
25979+
},
2596525980
"ClientInboundMessageTransfer": {
2596625981
"type": "object",
2596725982
"properties": {
@@ -26008,6 +26023,10 @@
2600826023
"$ref": "#/components/schemas/ClientInboundMessageSay",
2600926024
"title": "Say"
2601026025
},
26026+
{
26027+
"$ref": "#/components/schemas/ClientInboundMessageEndCall",
26028+
"title": "EndCall"
26029+
},
2601126030
{
2601226031
"$ref": "#/components/schemas/ClientInboundMessageTransfer",
2601326032
"title": "Transfer"
@@ -26601,6 +26620,263 @@
2660126620
"metadata"
2660226621
]
2660326622
},
26623+
"BashToolWithToolCall": {
26624+
"type": "object",
26625+
"properties": {
26626+
"async": {
26627+
"type": "boolean",
26628+
"description": "This determines if the tool is async.\n\nIf async, the assistant will move forward without waiting for your server to respond. This is useful if you just want to trigger something on your server.\n\nIf sync, the assistant will wait for your server to respond. This is useful if want assistant to respond with the result from your server.\n\nDefaults to synchronous (`false`).",
26629+
"example": false
26630+
},
26631+
"messages": {
26632+
"type": "array",
26633+
"description": "These are the messages that will be spoken to the user as the tool is running.\n\nFor some tools, this is auto-filled based on special fields like `tool.destinations`. For others like the function tool, these can be custom configured.",
26634+
"items": {
26635+
"oneOf": [
26636+
{
26637+
"$ref": "#/components/schemas/ToolMessageStart",
26638+
"title": "ToolMessageStart"
26639+
},
26640+
{
26641+
"$ref": "#/components/schemas/ToolMessageComplete",
26642+
"title": "ToolMessageComplete"
26643+
},
26644+
{
26645+
"$ref": "#/components/schemas/ToolMessageFailed",
26646+
"title": "ToolMessageFailed"
26647+
},
26648+
{
26649+
"$ref": "#/components/schemas/ToolMessageDelayed",
26650+
"title": "ToolMessageDelayed"
26651+
}
26652+
]
26653+
}
26654+
},
26655+
"type": {
26656+
"type": "string",
26657+
"enum": [
26658+
"bash"
26659+
],
26660+
"description": "The type of tool. \"bash\" for Bash tool."
26661+
},
26662+
"subType": {
26663+
"type": "string",
26664+
"enum": [
26665+
"bash_20241022"
26666+
],
26667+
"description": "The sub type of tool."
26668+
},
26669+
"toolCall": {
26670+
"$ref": "#/components/schemas/ToolCall"
26671+
},
26672+
"name": {
26673+
"type": "string",
26674+
"description": "The name of the tool, fixed to 'bash'",
26675+
"default": "bash",
26676+
"enum": [
26677+
"bash"
26678+
]
26679+
},
26680+
"function": {
26681+
"description": "This is the function definition of the tool.\n\nFor `endCall`, `transferCall`, and `dtmf` tools, this is auto-filled based on tool-specific fields like `tool.destinations`. But, even in those cases, you can provide a custom function definition for advanced use cases.\n\nAn example of an advanced use case is if you want to customize the message that's spoken for `endCall` tool. You can specify a function where it returns an argument \"reason\". Then, in `messages` array, you can have many \"request-complete\" messages. One of these messages will be triggered if the `messages[].conditions` matches the \"reason\" argument.",
26682+
"allOf": [
26683+
{
26684+
"$ref": "#/components/schemas/OpenAIFunction"
26685+
}
26686+
]
26687+
},
26688+
"server": {
26689+
"description": "This is the server that will be hit when this tool is requested by the model.\n\nAll requests will be sent with the call object among other things. You can find more details in the Server URL documentation.\n\nThis overrides the serverUrl set on the org and the phoneNumber. Order of precedence: highest tool.server.url, then assistant.serverUrl, then phoneNumber.serverUrl, then org.serverUrl.",
26690+
"allOf": [
26691+
{
26692+
"$ref": "#/components/schemas/Server"
26693+
}
26694+
]
26695+
}
26696+
},
26697+
"required": [
26698+
"type",
26699+
"subType",
26700+
"toolCall",
26701+
"name"
26702+
]
26703+
},
26704+
"ComputerToolWithToolCall": {
26705+
"type": "object",
26706+
"properties": {
26707+
"async": {
26708+
"type": "boolean",
26709+
"description": "This determines if the tool is async.\n\nIf async, the assistant will move forward without waiting for your server to respond. This is useful if you just want to trigger something on your server.\n\nIf sync, the assistant will wait for your server to respond. This is useful if want assistant to respond with the result from your server.\n\nDefaults to synchronous (`false`).",
26710+
"example": false
26711+
},
26712+
"messages": {
26713+
"type": "array",
26714+
"description": "These are the messages that will be spoken to the user as the tool is running.\n\nFor some tools, this is auto-filled based on special fields like `tool.destinations`. For others like the function tool, these can be custom configured.",
26715+
"items": {
26716+
"oneOf": [
26717+
{
26718+
"$ref": "#/components/schemas/ToolMessageStart",
26719+
"title": "ToolMessageStart"
26720+
},
26721+
{
26722+
"$ref": "#/components/schemas/ToolMessageComplete",
26723+
"title": "ToolMessageComplete"
26724+
},
26725+
{
26726+
"$ref": "#/components/schemas/ToolMessageFailed",
26727+
"title": "ToolMessageFailed"
26728+
},
26729+
{
26730+
"$ref": "#/components/schemas/ToolMessageDelayed",
26731+
"title": "ToolMessageDelayed"
26732+
}
26733+
]
26734+
}
26735+
},
26736+
"type": {
26737+
"type": "string",
26738+
"enum": [
26739+
"computer"
26740+
],
26741+
"description": "The type of tool. \"computer\" for Computer tool."
26742+
},
26743+
"subType": {
26744+
"type": "string",
26745+
"enum": [
26746+
"computer_20241022"
26747+
],
26748+
"description": "The sub type of tool."
26749+
},
26750+
"toolCall": {
26751+
"$ref": "#/components/schemas/ToolCall"
26752+
},
26753+
"name": {
26754+
"type": "string",
26755+
"description": "The name of the tool, fixed to 'computer'",
26756+
"default": "computer",
26757+
"enum": [
26758+
"computer"
26759+
]
26760+
},
26761+
"displayWidthPx": {
26762+
"type": "number",
26763+
"description": "The display width in pixels"
26764+
},
26765+
"displayHeightPx": {
26766+
"type": "number",
26767+
"description": "The display height in pixels"
26768+
},
26769+
"displayNumber": {
26770+
"type": "number",
26771+
"description": "Optional display number"
26772+
},
26773+
"function": {
26774+
"description": "This is the function definition of the tool.\n\nFor `endCall`, `transferCall`, and `dtmf` tools, this is auto-filled based on tool-specific fields like `tool.destinations`. But, even in those cases, you can provide a custom function definition for advanced use cases.\n\nAn example of an advanced use case is if you want to customize the message that's spoken for `endCall` tool. You can specify a function where it returns an argument \"reason\". Then, in `messages` array, you can have many \"request-complete\" messages. One of these messages will be triggered if the `messages[].conditions` matches the \"reason\" argument.",
26775+
"allOf": [
26776+
{
26777+
"$ref": "#/components/schemas/OpenAIFunction"
26778+
}
26779+
]
26780+
},
26781+
"server": {
26782+
"description": "This is the server that will be hit when this tool is requested by the model.\n\nAll requests will be sent with the call object among other things. You can find more details in the Server URL documentation.\n\nThis overrides the serverUrl set on the org and the phoneNumber. Order of precedence: highest tool.server.url, then assistant.serverUrl, then phoneNumber.serverUrl, then org.serverUrl.",
26783+
"allOf": [
26784+
{
26785+
"$ref": "#/components/schemas/Server"
26786+
}
26787+
]
26788+
}
26789+
},
26790+
"required": [
26791+
"type",
26792+
"subType",
26793+
"toolCall",
26794+
"name",
26795+
"displayWidthPx",
26796+
"displayHeightPx"
26797+
]
26798+
},
26799+
"TextEditorToolWithToolCall": {
26800+
"type": "object",
26801+
"properties": {
26802+
"async": {
26803+
"type": "boolean",
26804+
"description": "This determines if the tool is async.\n\nIf async, the assistant will move forward without waiting for your server to respond. This is useful if you just want to trigger something on your server.\n\nIf sync, the assistant will wait for your server to respond. This is useful if want assistant to respond with the result from your server.\n\nDefaults to synchronous (`false`).",
26805+
"example": false
26806+
},
26807+
"messages": {
26808+
"type": "array",
26809+
"description": "These are the messages that will be spoken to the user as the tool is running.\n\nFor some tools, this is auto-filled based on special fields like `tool.destinations`. For others like the function tool, these can be custom configured.",
26810+
"items": {
26811+
"oneOf": [
26812+
{
26813+
"$ref": "#/components/schemas/ToolMessageStart",
26814+
"title": "ToolMessageStart"
26815+
},
26816+
{
26817+
"$ref": "#/components/schemas/ToolMessageComplete",
26818+
"title": "ToolMessageComplete"
26819+
},
26820+
{
26821+
"$ref": "#/components/schemas/ToolMessageFailed",
26822+
"title": "ToolMessageFailed"
26823+
},
26824+
{
26825+
"$ref": "#/components/schemas/ToolMessageDelayed",
26826+
"title": "ToolMessageDelayed"
26827+
}
26828+
]
26829+
}
26830+
},
26831+
"type": {
26832+
"type": "string",
26833+
"enum": [
26834+
"textEditor"
26835+
],
26836+
"description": "The type of tool. \"textEditor\" for Text Editor tool."
26837+
},
26838+
"subType": {
26839+
"type": "string",
26840+
"enum": [
26841+
"text_editor_20241022"
26842+
],
26843+
"description": "The sub type of tool."
26844+
},
26845+
"toolCall": {
26846+
"$ref": "#/components/schemas/ToolCall"
26847+
},
26848+
"name": {
26849+
"type": "string",
26850+
"description": "The name of the tool, fixed to 'str_replace_editor'",
26851+
"default": "str_replace_editor",
26852+
"enum": [
26853+
"str_replace_editor"
26854+
]
26855+
},
26856+
"function": {
26857+
"description": "This is the function definition of the tool.\n\nFor `endCall`, `transferCall`, and `dtmf` tools, this is auto-filled based on tool-specific fields like `tool.destinations`. But, even in those cases, you can provide a custom function definition for advanced use cases.\n\nAn example of an advanced use case is if you want to customize the message that's spoken for `endCall` tool. You can specify a function where it returns an argument \"reason\". Then, in `messages` array, you can have many \"request-complete\" messages. One of these messages will be triggered if the `messages[].conditions` matches the \"reason\" argument.",
26858+
"allOf": [
26859+
{
26860+
"$ref": "#/components/schemas/OpenAIFunction"
26861+
}
26862+
]
26863+
},
26864+
"server": {
26865+
"description": "This is the server that will be hit when this tool is requested by the model.\n\nAll requests will be sent with the call object among other things. You can find more details in the Server URL documentation.\n\nThis overrides the serverUrl set on the org and the phoneNumber. Order of precedence: highest tool.server.url, then assistant.serverUrl, then phoneNumber.serverUrl, then org.serverUrl.",
26866+
"allOf": [
26867+
{
26868+
"$ref": "#/components/schemas/Server"
26869+
}
26870+
]
26871+
}
26872+
},
26873+
"required": [
26874+
"type",
26875+
"subType",
26876+
"toolCall",
26877+
"name"
26878+
]
26879+
},
2660426880
"StepDestination": {
2660526881
"type": "object",
2660626882
"properties": {

0 commit comments

Comments
 (0)