|
| 1 | +--- |
| 2 | +title: Changelog – 2025-06-20 |
| 3 | +--- |
| 4 | + |
| 5 | +# Changelog – 2025-06-20 |
| 6 | + |
| 7 | +## API Changes Overview |
| 8 | + |
| 9 | +This release brings significant enhancements for Vapi developers, with a focus on new campaign management, improved tool integration, and expanded credential support. Below is a summary of the most impactful changes since the last published changelog (2025-06-18): |
| 10 | + |
| 11 | +### 🚀 New Features |
| 12 | +- **Campaign Management API** |
| 13 | + - New endpoints and schemas for Campaign, CreateCampaignDTO, and UpdateCampaignDTO. |
| 14 | + - Enables scheduling, tracking, and managing outbound campaigns, including customer lists, schedule plans, and call assignment. |
| 15 | + - Campaigns now support status tracking (`scheduled`, `in-progress`, `ended`) and rich metadata (e.g., ended reason, calls counter). |
| 16 | +- **API Request Tool** |
| 17 | + - New `ApiRequestTool` schema and endpoints for defining and executing API requests within Vapi workflows. |
| 18 | + - Customizable headers, bodies, and variable extraction plans are now supported. |
| 19 | + - Enhanced error handling and retry logic via `backoffPlan`. |
| 20 | +- **Credential Management** |
| 21 | + - Added support for new credential types: S3, GCP, Azure, Supabase, Cloudflare, and more. |
| 22 | + - Credentials can be associated at the workflow and assistant levels, allowing dynamic credential injection and fallback ordering (`fallbackIndex`). |
| 23 | +- **Transcriber and Voice Enhancements** |
| 24 | + - Support for new transcriber providers and fallback plans, including AssemblyAI, Azure, Deepgram, and others. |
| 25 | + - Workflow and assistant schemas now include advanced voice and transcriber configuration, with fallback and denoising options. |
| 26 | + |
| 27 | +### 🛠️ Improvements |
| 28 | +- **Workflow & Assistant Schema Expansion** |
| 29 | + - Major expansion of `Workflow` and `Assistant` schemas to support: |
| 30 | + - Voice and transcriber selection |
| 31 | + - Credential and compliance plans |
| 32 | + - Real-time monitoring and observability (Langfuse integration) |
| 33 | + - Advanced speech denoising and artifact generation |
| 34 | +- **Client/Server Message Handling** |
| 35 | + - Expanded support for new message types and improved configuration of client/server message flows. |
| 36 | + - Enhanced template variable support for assistant messages using LiquidJS syntax. |
| 37 | +- **Error Handling** |
| 38 | + - Added and expanded `endedReason` enums for calls and campaigns, providing more granular error and status reporting. |
| 39 | + |
| 40 | +### 🧹 Removals |
| 41 | +- Deprecated and removed `model` property from `Workflow` schema. |
| 42 | +- Removed unused/legacy schema paths: `LogicEdgeCondition`, `FailedEdgeCondition`, `Workflow` (legacy versions). |
| 43 | + |
| 44 | +### 📝 Migration Notes |
| 45 | +- **Campaigns:** If you are using campaigns, review the new API endpoints and schemas. Campaigns now must be created and updated using the new DTOs and support richer scheduling and reporting. |
| 46 | +- **Credentials:** When using new credential types or fallback logic, ensure your workflow and assistant definitions are updated to reference the new credential schemas and properties. |
| 47 | +- **Tool Integrations:** If you build or use custom tools, review the new `ApiRequestTool` and related DTOs for expanded functionality and error handling. |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +For full details and schema references, see the [OpenAPI documentation](../openapi) and the updated developer guides. |
| 52 | + |
| 53 | +*Published: 2025-06-20* |
0 commit comments