Developers
Create and manage API keys to build custom integrations on top of Cloodot.
The Developers section is where admins manage programmatic access to Cloodot — creating API keys for custom integrations, scripts, or third-party tools that need to talk to your workspace.
Developer settings are available to admins and owners only.
Go to Settings → Developers → API Keys.
API Keys
Creating a key
- Click Create Key.
- Fill in the details in the drawer that opens:
- Name — A friendly label to help you remember what this key is for (for example, "Zapier integration" or "Internal reporting script").
- Expiration — Choose how long the key stays valid:
- Never
- 30 days
- 90 days
- 1 year
- Click Create Key.
Once the key is generated, you'll see the full value in a dialog with a Copy button.
This is the only time the full key will be shown. Copy it somewhere safe before closing the dialog — if you lose it, you'll need to delete the key and create a new one.
Click Done when you've stored the key securely.
Managing your keys
All of your existing keys appear in a table showing:
| Column | What it shows |
|---|---|
| Name | The friendly label you gave the key |
| Key | A masked preview (for example, clo_********) |
| Created | When the key was created |
| Expires | The expiration date, or "Never" |
| Status | Active (green) or Disabled (red) |
| Actions | Delete the key |
Deleting a key
Click the trash icon on any key to delete it. You'll see a confirmation prompt:
"Any applications using this key will lose access immediately. This action cannot be undone."
Click Delete to confirm.
Deleting a key is instant. Any scripts or integrations using it will start failing right away, so make sure nothing critical is relying on it first.
API Documentation
The Developers page links out to the full API Documentation, where you'll find:
- The complete REST API reference
- Authentication details
- Webhook setup and payloads
- Integration guides
Click the API Documentation card to open it in a new tab.
Keeping keys safe
- Never commit API keys to source control. Use environment variables or a secret manager.
- Scope by purpose. Create a separate key for each integration so you can revoke one without breaking the others.
- Set an expiration date whenever you can — it's a solid safety net against lost or forgotten keys.
- Rotate keys regularly, especially after a team member with access leaves your organization.
- Use the Logs page to spot unexpected activity on any key.
Related topics
- Developer Logs — Monitor API usage and errors
- Integrations — Connect Cloodot to your other tools without writing code
- MCP Servers — Extend Copilot with custom tools