I tried readding the webhook. It hasn't changed at all and i see in the webhooks logs that they aren't sending anymore.

Thank you for sharing the details. To help diagnose why webhooks aren't sending after enabling HIPAA mode, could you clarify if your webhooks are configured to receive any data that might include PHI (Protected Health Information)? This will help determine if HIPAA restrictions are affecting webhook delivery. If you need, I can also guide you on reviewing your assistant's webhook configuration settings. Sources: - [Vapi HIPAA Compliance Documentation](https://docs.vapi.ai/security-and-privacy/hipaa) - [Vapi Webhook Configuration](https://docs.vapi.ai/api-reference/assistants/update)

That doesnt matter

If you've switched on the HIPAA mode by enabling

hipaaEnabled

in your assistant settings, this prevents any call logs, recordings, or transcriptions from being stored. As a result, this may affect your webhook configurations. Ensure your webhooks are set to operate correctly in a HIPAA-enabled environment. To ensure compliance and proper functioning, your server endpoints should be configured properly with authentication, such as secret tokens or OAuth2, as described [here](https://docs.vapi.ai/server-url/server-authentication). Additionally, verify that the webhook endpoints you are using can handle the limited data that would be sent when HIPAA compliance is enabled. If the issue persists, you might need to review the settings or consider if there's a conflict with how webhooks are being managed alongside HIPAA-enabled configurations.

The issue was that the org level serverurl stopped working when hippaa was enabled and i had to add the serverUrl to each assistant indiviudally.

When HIPAA mode is enabled in Vapi AI, org-level serverUrl stops working, requiring the serverUrl to be set individually for each assistant with proper authenticated endpoints..