fix: add metadata field to CreateCallDTO schema#1027
Open
ghost wants to merge 1 commit into
Open
Conversation
Add top-level `metadata` field to CreateCallDTO, CreateOutboundCallDTO, and Call response schemas in the OpenAPI spec. This field was already present on CreateAssistantDTO and AssistantOverrides but missing from call-related schemas, causing all auto-generated SDKs (including .NET) to lack a metadata property on CreateCallDto. The field follows the same pattern as CreateAssistantDTO's metadata: a simple object type for storing arbitrary key-value metadata on calls. Linear: PRO-1773 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ghost
added
Contributor
|
🌿 Preview your docs: https://vapi-preview-c4e94d9b-4e4a-4510-92c0-85134522f3bd.docs.buildwithfern.com |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
metadatafield toCreateCallDTOschema in the OpenAPI specmetadatafield toCreateOutboundCallDTOschema for consistencymetadatafield toCallresponse schema so metadata set on create is returned on readCreateAssistantDTO's existing metadata field:{"type": "object", "description": "..."}metadataonCreateCallDto, which currently forces customers to extend the class manually or useAssistantOverrides.metadataas a workaroundLinear: PRO-1773
Testing Steps
fern check-- 0 errors (5 pre-existing warnings unrelated to this change)CreateAssistantDTOpatternfern docs devor navigate to preview deployment