Hi, I am testing the delete call api. It returns me the call data with 200 status code as shown in the API reference documentation. Ideally, it should not show up in the call logs or the "list" calls api response. However, I still find it. Can you tell me is the deletion of call logs not allowed? I pretty much double checked it. VAPI SERVER SDK TYPESCRIPT: ^0.2.2

@ChasingClouds Hello! In VAPI, the delete call API is designed to terminate an ongoing call rather than to delete a call log. If you're receiving a 200 status code, it means the request to terminate the call was successful, but it does not remove the record of the call from the logs. The call logs are typically maintained for auditing and historical purposes, and it's common for such logs not to be directly deletable via an API for data integrity and compliance reasons. If you need to manage or delete call logs for privacy or data retention policies, you may need to check if VAPI provides a different mechanism for that, such as through an admin panel or by contacting their support. If you believe the call should not appear in the "list" calls API response after using the delete call API, please ensure that you are using the correct endpoint and that the call has indeed been terminated. If the issue persists, it might be a good idea to reach out to VAPI support for further assistance. Please let me know if there's anything else I can help you with!

@ChasingClouds can you share the CURL request you're sending?

@Shubham Bajaj I am using the sdk for that "/delete" endpoint in the calls api. However, from the Support Bot request, it seems like that is more like termination of the call rather than the deletion of the call data. Is there any other endpoint through which i can trigger a call logs deletion? I am trying to build a wrapper around Vapi.

DELETE /call/:id is used for deleting call data instead of termination, so you're secure with this approach.