Capabilities

evre keeps the transactional send path open for every account. Advanced surfaces are capability-gated: new organizations start locked; a platform admin grants each key explicitly.

Key	Unlocks
`broadcast`	Broadcast routes, contacts/audiences write APIs, broadcast sends
`inbound`	Enable inbound receive on a domain, inbound routes
`webhooks`	Create webhook endpoints
`smtp_relay`	SMTP AUTH send
`custom_tracking_domain`	Project branded open/click tracking host
`template_editor`	Create and edit hosted templates (read/preview stay open)

Check your grants

curl https://api.evre.email/capabilities \
  -H "Authorization: Bearer $EVRE_API_TOKEN"

Response shape:

{
  "organizationId": "org_…",
  "capabilities": {
    "broadcast": false,
    "inbound": false,
    "webhooks": false,
    "smtp_relay": false,
    "custom_tracking_domain": false,
    "template_editor": false
  }
}

Request access

curl -X POST https://api.evre.email/capabilities/webhooks/request \
  -H "Authorization: Bearer $EVRE_API_TOKEN"

This writes an audit signal for platform admins. There is no automatic approval email.

SDKs

TypeScript: client.capabilities.get() / client.capabilities.request(key)
CLI: evre capabilities list / evre capabilities request <key>
Python / Go: same HTTP helpers on the client

Console

Locked pages show a Request access CTA. Admins grant keys under Admin → Organizations → Capabilities.