I am currently trying to implement structured output schema in the agent response. But it looks like there is an api error hitting while trying to create one Tried to use vapi sdk and got the error as below: raise ApiError(status_code=_response.status_code, headers=dict(_response.headers), body=_response_json) vapi.core.api_error.ApiError: headers: {'date': 'Thu, 23 Oct 2025 19:15:21 GMT', 'content-type': 'application/json; charset=utf-8', 'content-length': '87', 'connection': 'keep-alive', 'x-powered-by': 'Express', 'access-control-allow-origin': '*', 'x-robots-tag': 'noindex', 'etag': 'W/"57-TXCH3wKnwbC2P5/wyKGoUcqqAWw"', 'cf-cache-status': 'DYNAMIC', 'server': 'cloudflare', 'cf-ray': '9933900cdda9ec42-LHR', 'alt-svc': 'h3=":443"; ma=86400'}, status_code: 500, body: {'statusCode': 500, 'message': 'Internal server error. Contact support@vapi.ai for help.'} Also in API got the same error: ❌ Failed to create schema. Status Code: 500 {"statusCode":500,"message":"Internal server error. Contact support@vapi.ai for help."} {"statusCode":500,"message":"Internal server error. Contact support@vapi.ai for help."} Could you please have a look.

Internal Server Error (500) when creating a structured output schema is not expected and usually requires Vapi support intervention. Please email your error details (including the request payload and error message) to support@vapi.ai for direct assistance. Tip: You can also check your API logs in the [Vapi dashboard](https://dashboard.vapi.ai/) for more context, but contacting support is the fastest way to resolve backend errors. Sources: - [Structured outputs documentation](https://docs.vapi.ai/assistants/structured-outputs) - [Vapi debugging guide](https://docs.vapi.ai/debugging)

Hi Robin, Thanks for sharing those details. To help us investigate further, could you please provide: 1. The request payload you’re sending (feel free to paste it in a code block for clarity). 2. The exact API endpoint you’re calling when the error occurs. This will give us better context to trace what might be causing the 500 error. Best, Kyle