Skip to main content
Clawb can act as a backend enforcement point for email sending:
  1. Your service calls POST /v1/check with action: "send_email" and an email object (recipients, attachment metadata, etc.)
  2. If Clawb returns allow, your service calls POST /v1/email/send to send the email server-side via SendGrid
  3. If Clawb returns deny or challenge, your service must not send the email
Auth quick reference
Use provider keys with the ck_live_ or ck_test_ prefix.

Step 1 — Ask for a decision

Step 2 — Send (only if allowed)

/v1/email/send requires a workspace API key header.

Response

Blocked sends

If policy evaluation denies or challenges, /v1/email/send returns 403 with a stable payload: