Add changelog for January 11, 2025

Author: quantstruct[bot]

fern/changelog/2025-01-11.mdx

@@ -0,0 +1,109 @@
+
+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.
+
+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:
+
+```json
+{
+  "credentials": [
+    {
+      "provider": "deep-seek",
+      "apiKey": "YOUR_API_KEY",
+      "name": "YOUR_CREDENTIAL_NAME"
+    }
+  ],
+  "model": {
+    "provider": "deep-seek",
+    "model": "deepseek-chat"
+  }
+}
+```
+
+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.
+
+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.
+
+5. **Enhanced Call Transfer Options with SIP Verb**: You can now specify a `sipVerb` when defining a `TransferPlan` with `Assistant.model.tools[type=transferCall].destinations[type=sip].transferPlan` giving you the ability to specify the SIP verb (`refer` or `bye`) used during call transfers for greater control over call flow.
+
+6. **Azure Credentials and Blob Storage Support**: You can now configure Azure credentials with support for AzureCredential.service[service=blob_storage] service and use AzureBlobStorageBucketPlan withAzureCredential.bucketPlan, enabling you to store call artifacts directly in Azure Blob Storage.
+
+7. **Include 'ocpApimSubscriptionKey' for Azure OpenAI**: When configuring Azure OpenAI credentials, you can now include the AzureOpenAICredential.ocpApimSubscriptionKey to authenticate with Azure's OpenAI services.
+
+8. **New CloudflareR2BucketPlan**: You can now use CloudflareR2BucketPlan to configure storage with Cloudflare R2 buckets, enabling you to store call artifacts directly.
+
+9. **Enhanced Credential Support**: It is now simpler to configure provider credentials in `Assistant.credentials`. Additionally, credentials can be overridden with `AssistantOverride.credentials` enables granular credential management per assistant. Our backend improvements add type safety and autocompletion for all supported credential types in the SDKs, making it easier to configure and maintain credentials for the following providers:
+
+- S3Credential
+- GcpCredential
+- XAiCredential
+- GroqCredential
+- LmntCredential
+- MakeCredential
+- AzureCredential
+- TavusCredential
+- GladiaCredential
+- GoogleCredential
+- OpenAICredential
+- PlayHTCredential
+- RimeAICredential
+- RunpodCredential
+- TrieveCredential
+- TwilioCredential
+- VonageCredential
+- WebhookCredential
+- AnyscaleCredential
+- CartesiaCredential
+- DeepgramCredential
+- LangfuseCredential
+- CerebrasCredential
+- DeepSeekCredential
+- AnthropicCredential
+- CustomLLMCredential
+- DeepInfraCredential
+- SmallestAICredential
+- AssemblyAICredential
+- CloudflareCredential
+- ElevenLabsCredential
+- OpenRouterCredential
+- TogetherAICredential
+- AzureOpenAICredential
+- ByoSipTrunkCredential
+- GoHighLevelCredential
+- InflectionAICredential
+- PerplexityAICredential
+
+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:
+
+- UpdateBashToolDTO
+- UpdateComputerToolDTO
+- UpdateDtmfToolDTO
+- UpdateEndCallToolDTO
+- UpdateFunctionToolDTO
+- UpdateGhlToolDTO
+- UpdateMakeToolDTO
+- UpdateOutputToolDTO
+- UpdateTextEditorToolDTO
+- UpdateTransferCallToolDTO
+- BashToolWithToolCall
+- ComputerToolWithToolCall
+- TextEditorToolWithToolCall
+
+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:
+
+- UpdateToolCallBlockDTO
+- UpdateWorkflowBlockDTO
+- UpdateConversationBlockDTO
+
+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:
+
+- UpdateByoPhoneNumberDTO
+- UpdateTwilioPhoneNumberDTO
+- UpdateVonagePhoneNumberDTO
+- UpdateVapiPhoneNumberDTO
+
+When updating phone numbers, developers should now use specific DTOs such as `UpdateTwilioPhoneNumberDTO` instead of the generic `UpdatePhoneNumberDTO`.
+
+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:
+
+- UpdateCustomKnowledgeBaseDTO
+- UpdateTrieveKnowledgeBaseDTO