Write to Sendly support
Emails the support inbox, with the person's account email as Reply-To. An API key has no account email, so it sends wantsReply: false. Attachments are https links the support team opens; nothing fetches them. Ten tickets per caller per hour.
Requires the support:write scope — Open support tickets and suspension appeals.
AuthorizationBearer <API Key>API key authentication. Use a sk_* (FULL) or pk_* (SENDING_ONLY) key as the bearer token. Public keys (pk_*) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by /api/v1/* operations): FULL keys hold every scope; SENDING_ONLY keys hold only emails:send.
application/json- body
subject*string1 <= length <= 200body*string1 <= length <= 4000type?string"question""problem""feature""question""other"attachments?array<>items <= 5wantsReply?booleantrueOK
application/json- response
ticketId*stringstatus*stringsent: the support inbox got it. logged: it was recorded but the email failed; support still sees it.
"sent""logged"curl -X POST 'https://api.sendly.now/api/v1/support/tickets' \ -H 'Content-Type: application/json' \ -d '{ "subject": "string", "body": "string"}'{ "ticketId": "string", "status": "sent"}