Structure
API Keys Pages
Section titled API Keys PagesOpen API Keys from the left sidebar to manage your keys.
Page | URL | Purpose |
|---|---|---|
Key list |
| View all keys for your team |
Create key |
| Set up a new key |
Key details |
| Edit permissions, regenerate, or delete |
Key list

The list shows each key's name, creation date, and how many integrations (apps) are configured.
From here you can:
Create New API Key — start the setup wizard
Edit — change name, apps, components, or connections
Regenerate Key — issue a new secret (the previous one stops working)
The secret value is never shown on this page — only when a key is first created or regenerated.
Create a key

What you configure
Field | Required | Description |
|---|---|---|
Key name | Yes | A label for your reference |
Integrations | Yes (at least one app) | Apps this key may access |
Components | Yes, per app | Specific actions/triggers the key may run |
Connection | When the app requires sign-in | Which connected account Monkedo should use |
Example of what gets saved:
{
"name": "Production API Key",
"connections": [
{
"appKey": "gmail",
"connectionId": "507f1f77bcf86cd799439011",
"allowedComponents": ["action.gmail.send-email"]
}
]
}Setup flow
Enter a Key Name.
Under Integrations, search for and select an app.
A Configure window opens — choose components and, if needed, a connection.
Repeat for any additional apps.
Click Create API Key once every app shows as configured.
Copy the key immediately — you won't be able to view it again after closing the dialog.
Key Details (edit)

The edit page lets you change integrations the same way as during creation. You can also:
Action | What happens |
|---|---|
Regenerate | A new secret is issued; the old one stops working right away |
Configure / Remove app | Changes are saved when you update an app's settings |
Delete API Key | The key is removed permanently and stops working immediately |
Removing an app from a key also removes any triggers that were registered for that app under this key.
Configure App (modal)

Each app opens a configuration dialog with two parts.
Components
Choose which actions and triggers this key may use for the app.
Check individual components, or use Select All.
Only selected components are callable through the API.
Connection
Shown when the app requires authentication (OAuth, API key, credentials, etc.).
Select the components you need first.
Click Get Connections to see accounts that support those components.
Pick an existing connection or click Connect {App} to link a new account.
Monkedo flags connections that are expired or missing permissions, so you can pick a working account before saving.
Save is enabled when:
At least one component is selected, and
A connection is selected if the app requires one