Hello. I have a dotnet endpoint that is trying to deserialize the payload, but I cannot get the schema correct. Please give us a payload schema of the body that VAPI sends to a post url from tool webhooks.

@Hew Certainly! The payload schema that VAPI sends to a POST URL typically includes several fields that provide information about the event that triggered the webhook. While I don't have the exact schema details, a common webhook payload from a Voice API might include the following fields: - `event`: The type of event that occurred (e.g., call started, call ended, etc.). - `callId`: A unique identifier for the call. - `timestamp`: The time at which the event occurred. - `direction`: Indicates whether the call is inbound or outbound. - `from`: The caller's phone number or identifier. - `to`: The recipient's phone number or identifier. - `duration`: The duration of the call (for call ended events). - `status`: The status of the call (e.g., completed, failed, etc.). - `recordingUrl`: A URL to access the call recording (if applicable). - `transcription`: The text transcription of the call (if available). Please note that the actual fields and structure of the payload can vary based on the specific implementation of VAPI. If you need the exact schema for your former endpoint, you may need to refer to the documentation provided by the VAPI service or contact their support for more detailed information. If you have access to the server URL or any other specific details that could help me provide a more accurate schema, please share them, and I'll be happy to assist further.

@Hew check ServerMessageToolCall from here https://api.vapi.ai/api#/Assistants/AssistantController_findOne