DevelopersGuides
Security
How AssistCall protects the API keys you create and the data they reach, and what you can do on your side. If you find a security problem, please tell us at [email protected].
On this page
Keys and tokens
- Secrets are shown once. A client secret appears only when its key is created. We store a keyed hash of it (HMAC-SHA256 with a server-side key that isn't in the database), plus its last four characters for display. Nobody, including AssistCall staff, can read it back.
- Access tokens are short-lived and hashed. Tokens last one hour and are stored the same way. A database copy alone can't be used to call the API.
- Revoking is immediate. Revoking a key ends every token it was given.
- Guessing is throttled. Secrets are compared in constant time, and an address that fails 10 times in 10 minutes is blocked for 10 minutes.
- Least privilege. Each key carries only the scopes it was given, can be limited to IP addresses, and only account owners can create or revoke keys. Read-only demo logins can't create keys at all.
Account isolation
- Every request is limited to the account (or partner) the token belongs to. That comes from the token on our side, never from ids in the request, so a path or body can't reach another account's data.
- An id that belongs to a different account answers
404, exactly like one that doesn't exist, so ids can't be probed. - Partner keys reach only that partner's own clients, one named client per request. A partner's clients don't get API keys of their own, and can't see each other or their partner's account. See Partner API.
- Keys of accounts that are suspended, canceled or not yet set up are refused, as are writes to a partner's client that isn't active.
Encryption in transit
- The API, the dashboards and these docs are served only over HTTPS (TLS 1.2 or 1.3), with HSTS. Plain HTTP isn't answered with data.
- Webhooks are only sent to
https://URLs and are signed (verify every one). We refuse to send them, or the AI Employee's live API actions, to private, loopback or link-local addresses, including names that resolve to one.
How the API is run
- The public API is a separate service from the dashboards, with its own connection limits, timeouts and rate limits, so heavy API use can't slow down call handling or the portals.
- It uses bearer tokens only: it doesn't read or set cookies. Browsers can call it only from this docs site's Try it console, without credentials.
- Request bodies are limited to 100 KB, every request has a 25-second limit, and unknown parameters are refused rather than ignored.
- We log each request's method, path (without the query string), status, timing and IP address for 7 days, to run the service and show you your recent requests. Request and response bodies aren't logged.
What you can do
- Keep client secrets and tokens on your server, in environment variables or a secret manager; never in a web page, app or repository.
- Create one key per app with only the scopes it needs, and use IP allowlists where your servers have fixed addresses.
- Rotate keys regularly, and revoke a key the moment you think its secret may have leaked.
- Verify the signature and timestamp of every webhook.
- Remember that call transcripts, recordings and messages can contain personal information. Store only what you need, protect it like your own customer data, and delete it when you no longer need it.
AssistCall doesn't sign HIPAA business associate agreements. Don't use the API or integrations to move protected health information.
Reporting a vulnerability
Email [email protected] with "Security report" in the subject. Include what you found, how to reproduce it, and any request ids. We'll confirm we've received it and keep you updated while we fix it.
While you look, please:
- use your own account, or sandbox credentials we share on request, and never access, change or keep other people's data;
- don't run tests that degrade the service for others (load tests, spam, social engineering of our staff or customers);
- give us reasonable time to fix the problem before telling anyone else about it.