It sounds like you're running into a common issue where the DELETE API call returns a 200 status but the knowledge base isn't actually being deleted. Here are a few things to check:
1. **Soft Delete vs. Hard Delete**: Sometimes, the API might be performing a soft delete, which means the knowledge base is not fully removed from the system. You may need to perform a hard delete from the backend. If this is the case, contacting VAPI support might be necessary for complete removal.
2. **Response Processing Issues**: Ensure that the response from the API is formatted correctly. Issues like extra spaces in the JSON response or incorrect content-type settings can lead to unexpected behaviors.
3. **Cache Problems**: Sometimes, caching issues can make it seem like the knowledge base still exists. Try checking in different browsers or clearing your cache to see if that resolves the issue.
4. **Authorization and Permissions**: Make sure that the Bearer token you are using has the necessary permissions to delete the knowledge base. If the token is invalid or lacks the right permissions, it could lead to issues.
5. **Check Server Logs**: If possible, access the server logs to see if there are any errors or discrepancies that could indicate why the deletion isn't happening.
If you've checked all these and are still having trouble, it might be best to reach out to VAPI support with the details of your API calls and the knowledge base ID you're trying to delete. They can provide more specific guidance based on your situation. Let me know if you need any more help! 😊
Sources:
- [Common Reasons for a DELETE API Call Returning a 200 Status](
https://discord.com/channels/1211482211119796234/1211483291191083018/1337314227857391627)
- [Troubleshooting Issues with the Delete API Call](
https://docs.vapi.ai/api-reference/knowledge-bases/delete)
- [Detailed Report on Deleting a Knowledge Base in Vapi](
https://docs.vapi.ai/api-reference/knowledge-bases/delete)