rubber-blueR
VAPI2mo ago
rubber-blue

Vapi HIPAA Compliance Storage

Hello Vapi,

We are trying to configure custom S3 storage for a HIPAA compliant workflow with Vapi.

We’ve already enabled HIPAA compliance and understand that Vapi can push call recordings and transcripts to a self-hosted S3-compatible endpoint.

However, it’s unclear how to provide a custom endpoint URL for Vapi to push recordings to our storage server. Right now, we are using MinIO for S3 compatible storage, but we need to know how to get Vapi to point to this rather than using AWS S3.

For context, our MinIO server is hosted on our own server, is reachable via HTTPS (we’ve whitelisted storage.vapi.ai), and configured with access and secret keys that mimic AWS S3 authentication.

This is what support has told us to use:

{
"provider": "s3",
"name": "Internal MinIO Storage",
"awsAccessKeyId": "<ACCESS_KEY>",
"awsSecretAccessKey": "<SECRET_KEY>",
"region": "us-east-1",
"s3BucketName": "recordings",
"s3PathPrefix": "vapi/",
"endpointUrl": https://portal.myhealthcarestartup.com:9800/
}

and were told to post the request to https://api.vapi.ai/credential but the API tells us endpointUrl is not a valid parameter.

What is the exact parameter name and format used to specify the URL of a self-hosted MinIO server in the storage configuration?

Thank you!
Was this page helpful?