Skip to content

Commit b2178f6

Browse files
Update changelog for January 11, 2025
1 parent 7fea9bd commit b2178f6

File tree

1 file changed

+5
-16
lines changed

1 file changed

+5
-16
lines changed

fern/changelog/2025-01-11.mdx

Lines changed: 5 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
21
1. **Integration of Smallest AI Voices**: Assistants can now utilize voices from Smallest AI by setting the voice provider to `Assistant.voice[provider="smallest-ai"]`, allowing selection from a variety of 25 preset voices and customization of voice attributes.
32

43
2. **Support for DeepSeek Language Models**: Developers can now configure assistants to use DeepSeek LLMs by setting the `Assistant.model[provider="deep-seek"]` and `Assistant.model[model="deepseek-chat"]`. You can also specify custom credentials by passing the following payload:
@@ -19,7 +18,7 @@
1918
}
2019
```
2120

22-
3. **Additional Call Ended Reasons for DeepSeek and Cerebras**: New `endedReason` enums have been added to handle specific DeepSeek and Cerebras call termination scenarios, allowing developers to better manage error handling.
21+
3. **Additional Call Ended Reasons for DeepSeek and Cerebras**: New `Call.endedReason` have been added to handle specific DeepSeek and Cerebras call termination scenarios, allowing developers to better manage error handling.
2322

2423
4. **New API Endpoint to Delete Logs**: A new `DELETE /logs` endpoint has been added, enabling developers to programmatically delete logs and manage log data.
2524

@@ -72,10 +71,10 @@
7271
- InflectionAICredential
7372
- PerplexityAICredential
7473

75-
10. **Specify Type When Updating Tools**: You should now [update tools](https://api.vapi.ai/api#/Tools/ToolController_update) by specifying the tool type in the request body using the appropriate payload for the tool type. Specifying the type now provides type safety and autocompletion in the SDKs. Refer to [schemas for the following tools](https://api.vapi.ai/api) to see the expected payload:
74+
10. **Specify Type When Updating Tools, Blocks, Phone Numbers, and Knowledge Bases**: You should now specify the type in the request body when [updating tools](https://api.vapi.ai/api#/Tools/ToolController_update), [blocks](https://api.vapi.ai/api#/Blocks/BlockController_update), [phone numbers](https://api.vapi.ai/api#/Phone%20Numbers/PhoneNumberController_update), or [knowledge bases](https://api.vapi.ai/api#/Knowledge%20Base/KnowledgeBaseController_update) using the appropriate payload for each type. Specifying the type now provides type safety and autocompletion in the SDKs. Refer to [the schemas](https://api.vapi.ai/api) to see the expected payload for the following types:
7675

7776
- UpdateBashToolDTO
78-
- UpdateComputerToolDTO
77+
- UpdateComputerToolDTO
7978
- UpdateDtmfToolDTO
8079
- UpdateEndCallToolDTO
8180
- UpdateFunctionToolDTO
@@ -87,23 +86,13 @@
8786
- BashToolWithToolCall
8887
- ComputerToolWithToolCall
8988
- TextEditorToolWithToolCall
90-
91-
11. **Specify Type When Updating Blocks**: You should now [update blocks](https://api.vapi.ai/api#/Blocks/BlockController_update) by specifying the block type in the request body using the appropriate payload for the block type. Specifying the type now provides type safety and autocompletion in the SDKs. Refer to [the following schemas](https://api.vapi.ai/api) to see the expected payload:
92-
9389
- UpdateToolCallBlockDTO
9490
- UpdateWorkflowBlockDTO
9591
- UpdateConversationBlockDTO
96-
97-
12. **Specify Type When Updating Phone Numbers**: You should now [update phone numbers](https://api.vapi.ai/api#/Phone%20Numbers/PhoneNumberController_update) by specifying the phone number type in the request body using the appropriate payload for the phone number type. Specifying the type now provides type safety and autocompletion in the SDKs. Refer to [the following schemas](https://api.vapi.ai/api) to see the expected payload:
98-
9992
- UpdateByoPhoneNumberDTO
10093
- UpdateTwilioPhoneNumberDTO
10194
- UpdateVonagePhoneNumberDTO
10295
- UpdateVapiPhoneNumberDTO
103-
104-
When updating phone numbers, developers should now use specific DTOs such as `UpdateTwilioPhoneNumberDTO` instead of the generic `UpdatePhoneNumberDTO`.
105-
106-
13. **Specify Type When Updating Knowledge Bases**: You should now [update knowledge bases](https://api.vapi.ai/api#/Knowledge%20Base/KnowledgeBaseController_update) by specifying the knowledge base type in the request body using the appropriate payload for the knowledge base type. Specifying the type now provides type safety and autocompletion in the SDKs. Refer to [the following schemas](https://api.vapi.ai/api) to see the expected payload:
107-
10896
- UpdateCustomKnowledgeBaseDTO
109-
- UpdateTrieveKnowledgeBaseDTO
97+
- UpdateTrieveKnowledgeBaseDTO
98+

0 commit comments

Comments
 (0)