Skip to Content
SendlySendly
API ReferenceSupport

Write to Sendly support

POST
/api/v1/support/tickets

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.

headerAuthorizationBearer <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
  1. body
subject*string
Length1 <= length <= 200
body*string
Length1 <= length <= 4000
type?string
Default"question"
Value in"problem""feature""question""other"
attachments?array<>
Itemsitems <= 5
wantsReply?boolean
Defaulttrue

Response Body

OK

application/json
  1. response
ticketId*string
status*string

sent: the support inbox got it. logged: it was recorded but the email failed; support still sees it.

Value in"sent""logged"
Example Request
curl -X POST 'https://api.sendly.now/api/v1/support/tickets' \  -H 'Content-Type: application/json' \  -d '{  "subject": "string",  "body": "string"}'
Example Response
{  "ticketId": "string",  "status": "sent"}