Zapier connects to Diobox using an API key. This article explains how API keys work and how to create, view, replace and delete them.
In This Article
How API Keys Work
Each API key is created inside a single event and can access only that event's data. A key created for one event cannot read or change guests in any other event in your account. If a key is exposed, the impact is limited to that event, and you can revoke it without affecting your other events.
You can create one or more keys per event. Using a separate key for each Zap or each team lets you revoke access to one workflow without interrupting the others.
API keys can be created and managed by Account Owners, Account Admins and Event Admins.
Create an API Key
Step 1 – In your event, go to Event Settings → Integrations.
Step 2 – In the Zapier section, click New API Key. Enter a name that describes what the key will be used for, for example:
Add Leadership Summit guests to Google Sheets
Add new registrations to Mailchimp
Send guest check-ins to Slack
HubSpot sync
A descriptive name makes it easier to identify the key later, when reviewing activity or deleting keys that are no longer needed.
Step 3 – Copy the key and store it securely, for example in a password manager.
The full API key is shown only once. After you close the dialog, Diobox displays only the last characters of the key. If you lose the key, delete it and create a new one.
This is a security measure. Other collaborators on the event can see the Integrations page, but not the complete key. If a collaborator's Diobox account is later removed, they do not retain a copy of a key that would still give them remote access to the event.
Step 4 – When you add a Diobox step to a Zap, select Sign in under Account and paste the key. The connection is listed in Zapier under your event's name.
View API Keys
All keys for the event are listed in the Zapier section of Event Settings → Integrations:
Name – the name entered when the key was created
Created On – the date and time the key was created
API Key – the last characters of the key, for identification
Last Used – the last time Zapier used the key; Never means it has not been used yet
Use Last Used to confirm a key is active, or to find keys that are no longer in use.
Delete an API Key
In Event Settings → Integrations, click the delete icon next to the key.
Deleting a key revokes access immediately:
Any Zap using the key stops running and shows an authentication error in Zapier.
The key cannot be restored. To reconnect, create a new key.
Before deleting a key that is in use, turn off or update the Zaps that depend on it.
Best Practices
Use one key per workflow. Separate keys let you revoke one integration without affecting others.
Use descriptive names. Name each key after the Zap or team that uses it.
Store keys securely. Do not share keys by email or chat. Anyone with the full key can view and change guests in the event.
Review keys regularly. Check Last Used and delete keys that are no longer needed.
Replace keys when access changes. If someone who had a copy of a key leaves your team, replace the key.