Skip to main content
A blocked email cannot book a meeting or buy a package. Emails are stored lowercased and without +tags, and Gmail addresses without dots, so John.Doe+promo@gmail.com is stored as johndoe@gmail.com. You need the Manage blocked emails permission to run these commands. For fields and response details, see the API reference. Sample output on this page uses --json.

List blocked emails

This command lists the workspace’s blocked emails, newest first. Use this to find a blocked email’s ID or to check whether an email is blocked.
Sample output (--json)
--search is normalized the same way as stored emails, so Gmail dots and +tags do not matter.

Show a blocked email

This command shows one blocked email. Use this after finding its ID from blocked-emails list.
Required arguments:
  • <id> - Blocked email UUID
Sample output (--json)

Block emails

This command blocks one or more emails with an optional note. Emails that are already blocked are left as they are, note included. If any email is invalid, none are blocked.
Sample output (--json)
The output lists each distinct email once, sorted by address, whether newly blocked or already blocked.

Update a blocked email

This command changes the note on a blocked email. The email itself cannot be changed. To change it, block the new email and delete this one.
Required arguments:
  • <id> - Blocked email UUID
Sample output (--json)

Delete a blocked email

This command unblocks an email so it can book meetings and buy packages again.
Required arguments:
  • <id> - Blocked email UUID
Sample output
In --quiet mode, this prints success.