API keys
Create a personal API key to connect automation tools and your own scripts to VoiceCap.
An API key lets an automation tool, such as Zapier, Make or n8n, or a script of your own read your meetings, decisions and action items, and get told when a meeting is ready. A key acts as you, in one organization, and sees exactly what you can open in VoiceCap. Nothing more.
Creating a key
- Open Settings > Profile.
- In API keys, click Create API key.
- Name the key after where you'll use it, such as Zapier, and click Create.
- Copy the key and click Done.
VoiceCap shows the key once. If you lose it, revoke it and create a new one. Your list shows each key's name, its first and last characters, and when it was last used. A key you made in another organization is listed too, with that organization's name, so you can revoke it from here.
Every time a key is created on your account, VoiceCap emails you its name and its first and last characters. If you didn't create it, revoke it and change your password.
You need a verified email address to create a key, and you can have up to 10 at a time. Any member can create one, Viewers included. A Viewer's key reads what the Viewer can read.
What a key can do
A key reads meetings, transcripts, summaries, decisions, action items and groups, exports meetings, and sets up notifications for new meetings, decisions and action items. Those notifications are the only thing it creates or removes. It can't change, share or delete meetings, and it can't reach your account or organization settings.
A key belongs to the organization you had open when you created it. If you switch to another organization, it stops working until you switch back.
When a key stops working
- You click Revoke next to it. Any automation that used it stops too.
- You leave the organization. Every key you made there is revoked.
- You reset or change your password. Every key you have, in every organization, is revoked.
- An Owner or Admin revokes it, or turns API keys off.
For owners and admins
At Settings > Integrations, the API keys card lists every member's keys with when each was last used, and a Revoke button for each one.
The Allow API keys switch is on by default. Turning it off stops every key in the organization right away without deleting them, and turning it back on restores them. While keys are off, members can't create new ones, and automations don't receive anything that happens in the meantime.