APIs and webhooks let your own systems read from and react to Frosvo.
Create an API key
- Go to Settings → API as an owner.
- Create a key and choose its scopes, the narrowest set that does the job.
- Copy the key when it is shown and store it in a safe place such as a secrets manager.
- Call the REST API with the key. The full reference is on the developers page and in the OpenAPI description.
You can create several keys, one per system, and delete one without affecting the others.
Add a webhook
- Open the webhook settings.
- Enter an https address on your server that can receive POST requests.
- Choose the events you want, such as new conversations, new messages, conversations resolved or rated, and missed deadlines.
- Save, and copy the signing secret.
Check the signature on every request, and answer quickly with a success status.
Retries and replays
If your server is down, Frosvo retries for about two days. Events can be replayed, so a gap in your system is recoverable. A webhook that keeps failing is switched off and appears on the Problems page.
Keep it safe
- Never put a key in a web page or source code.
- Rotate a key you suspect leaked: create a new one, switch over, delete the old one.
- Review keys and webhooks from time to time in the audit log.
Related
See the developer overview, connect chat tools with Slack and the account connector, or use ready-made tools from plugins. Read about account security.
Common questions
Which should I use, the API or a webhook? Use the API when your system needs to ask Frosvo for something, and a webhook when Frosvo should tell your system the moment something happens. Many integrations use both.
Can I test a webhook? Point it at a test address you control, trigger the event in a test conversation, and check that your server verified the signature and answered quickly.