CarlyEmail docs
Email support@carlyemail.com. One person reads it, so a clear subject line genuinely helps.
What to include
The single most useful thing is the request id. Every response carries one, and it lets us find your exact request rather than guessing from a description.
x-amzn-requestid: 4c7f1a2e-...
Failing that: your organization id (org_…), the endpoint, roughly when it
happened, and the full error body — the code field in particular.
Warning
Never send us an API key. We cannot read one anyway — keys are stored only as a
hash — and a key in an email is a key in an email forever. If you think one has
leaked, revoke it with DELETE /v0/api-keys/{id} and issue another.
Mail that did not arrive
Check GET /v0/inboxes/{id}/events first. Every send, delivery, bounce and
complaint is recorded there before any webhook is attempted, so it will usually
tell you what happened without us being involved — including whether the address
is on your suppression list.
Security
Suspected vulnerabilities go to the same address and get acknowledged within two business days. See security.