Account & Integrations
By Maildesk Team ·
Invite Your Team, Webhooks & API Keys
Add workspace members with the right roles, get notified of subscriber events via webhooks, and find your API keys.
Once the basics are running, three settings pages connect Maildesk to the rest of your operation: your team, your systems, and your code.
Invite workspace members
- Go to Settings > Workspace.
- Click to invite a member, enter their email, and pick a role.
- The invitee gets an email with an acceptance link. Pending invitations are listed on the same page, where you can resend or revoke them.
The three roles
| Role | Can do |
|---|---|
| Admin | Everything — including billing, workspace management, and deletions |
| Manager | Manage contacts, campaigns, forms, automations, and templates, and send emails |
| Member | Read-only access |
You can change a member’s role or remove them from the members table at any time. Give people the least role that lets them do their job — most collaborators only need Manager.
Set up webhooks
Webhooks push subscriber events to your systems in real time — keeping a CRM in sync, updating your product database, or triggering your own workflows.
- Go to Settings > Webhooks.
- Create a webhook with your Endpoint URL (e.g.
https://example.com/webhook) and select the events to receive.
Two events are currently available:
| Event | Fires when |
|---|---|
subscriber.confirmed | A subscriber confirms their subscription |
subscriber.unsubscribed | A subscriber opts out |
Each webhook has a detail page showing its status, event types, and a Webhook Logs table with every delivery marked Succeeded or Failed — expand a row to inspect the exact payload. You can edit the endpoint, change events, or disable the webhook without deleting it, and there’s a ping option to test your endpoint.
Find your API keys
Go to Settings > API Keys. Every business has two pre-issued keys:
- Public Key (
pk_…) - Secret Key (
sk_…)
Both are masked with a copy button. Use the secret key as a Bearer token for the API — endpoints for subscribers and tags are documented at maildesk.apidog.io.
Keep the secret key secret. Anyone holding it can read and modify your subscriber list. Keys can’t currently be rotated from the UI, so never commit them to code repositories or share them in chat — store them in environment variables.
A common pattern that puts all three together: your product calls the API to create contacts when users sign up (with a tag that triggers a welcome sequence), and a webhook on subscriber.unsubscribed keeps your product’s notification settings in sync.
← Back to guides