Skip to content

Beta: these docs are still being updated. The next full update is on 18 November at 8 PM UTC. Docs in beta. Full update 18 Nov, 8 PM UTC.

Hoody.com

Lookup tables for support. Every parameter and response field is in the Support tickets API reference.

All nine operations are in the CLI (hoody support) and the SDK (client.api.support). Every answer, refusals included, carries Cache-Control: no-store.

What it doesMethod and pathCLISDK
Open a ticket with its first messagePOST /api/v1/support/ticketshoody support createtickets.create
List your tickets, most recent message firstGET /api/v1/support/ticketshoody support listtickets.list
Tickets changed since your last pollGET /api/v1/support/tickets/changeshoody support changes listtickets.listChanges
One ticket with its messages (marks it read)GET /api/v1/support/tickets/{id}hoody support gettickets.get
Add a message to a ticketPOST /api/v1/support/tickets/{id}/messageshoody support replytickets.reply
Close a ticket (no request body); the CLI asks for confirmationPOST /api/v1/support/tickets/{id}/closehoody support closetickets.close
Find the ticket a create with this client_key madeGET /api/v1/support/tickets/by-keyhoody support keys gettickets.getByKey
Find the reply a client_key added to a ticketGET /api/v1/support/tickets/{id}/messages/by-keyhoody support messages keys gettickets.getMessageByKey
Your limits and what is used nowGET /api/v1/support/limitshoody support limits getgetLimits

Who can use support is on the guide. Refusals:

CallerResult
Auth token without resources.support, or limited to realms403
HTTP Basic credentials, an impersonated session, a realm host403 INSUFFICIENT_PERMISSIONS
Admin or platform account403 SUPPORT_NOT_FOR_ACCOUNT
Staff accountRefused earlier: 403 STAFF_ACCOUNT_SCOPE with a signed-in session, 401 STAFF_JWT_REQUIRED with an auth token
ItemRule
SubjectOne line of up to 200 characters
MessageUp to 4,000 characters, 200 lines and 16,000 bytes of UTF-8, with no single line longer than 2,000 characters
FormatPlain text: nothing is rendered as HTML or Markdown, and there are no attachments or images
Far over the sizeA subject over 2,000 characters or a message over 16,000 characters as sent is refused before the text check, with 400 SUPPORT_FIELD_INVALID

Harmless noise is cleaned before the text is stored, and each rule that changed something is listed in cleaned. A field that was stored exactly as sent is absent from cleaned.

RuleWhat it does
C1Turns every line-ending form into a single line feed
C2Applies Unicode NFC normalisation
C3Removes spaces and tabs at the end of each line
C4Trims the subject; removes blank lines at the start and end of a message
C5Reduces more than two blank lines in a row to two
C6Removes invisible copy-paste debris such as zero-width spaces, soft hyphens and byte order marks
C7Removes joiners and variation selectors outside the places a script or an emoji needs them

The create answers 201 with the ticket, its first message and cleaned:

{
"statusCode": 201,
"message": "Support ticket created",
"data": {
"ticket": { "id": "6720a1b2c3d4e5f6a7b8c9d0", "subject": "Computer will not start after resize", "category": "computers", "status": "open", "terminal": false, "unread": false, "created_at": "2026-10-28T09:15:00.000Z", "last_message_at": "2026-10-28T09:15:00.000Z", "closed_at": null, "reopenable": false },
"message": { "id": "6720a1b2c3d4e5f6a7b8c9d1", "seq": 1, "from": "you", "body": "Since resizing to 4 GB my computer stays in \"starting\". Started 09:00 UTC.", "created_at": "2026-10-28T09:15:00.000Z" },
"cleaned": {}
}
}

Characters that hide or reorder text are refused rather than removed. A refusal is 400 SUPPORT_TEXT_INVALID, and the error never repeats your text:

{
"statusCode": 400,
"error": "SUPPORT_TEXT_INVALID",
"message": "body is not accepted as plain text.",
"data": { "field": "body", "rule": "too_long", "at": "cleaned", "index": 4000 }
}
data fieldMeaning
fieldsubject or body
ruleThe check that failed (below)
atinput (the text as sent) or cleaned (after cleaning)
indexThe character offset of the problem
ruleMeaning
too_long, too_many_lines, line_too_longOver a size limit
emptyNothing visible is left
multilineA line break in the subject
lone_surrogate, nul, escape, c0_control, c1_controlControl characters
bidi_control, invisible_char, tag_charCharacters that hide or reorder text
private_use, noncharacterCode points with no public meaning
combining_floodToo many combining marks on one character

Statuses and reopening are on the guide. Each ticket also has fixed size limits:

EventEffect
Reply more than 30 days after closing409 SUPPORT_TICKET_EXPIRED: open a new ticket
50 of your messages on one ticketYou can send at most 50 messages on one ticket; more answer 409 SUPPORT_TICKET_LIMIT
Message 100 of the ticketA ticket holds at most 100 messages in total. The write that takes message 100 closes the ticket for good: terminal becomes true, nothing can reopen it, and it stays readable; later replies answer 409 SUPPORT_TICKET_FULL
198th status changeCloses the ticket for good. Every close, reopen, automatic close and switch between open and waiting_user counts as one; later replies answer 409 SUPPORT_TICKET_FULL

On a ticket closed for good, resending your own latest message within 60 seconds answers 409 SUPPORT_DUPLICATE instead; see Duplicate text.

tierWhen
paidWhile the account has a server subscription or a server rental that is active or in billing trouble
freeOtherwise
bannedA banned account: the free limits, with one open ticket and two new tickets a day

The limits table on the guide shows the default values; the deployment can change them, and GET /api/v1/support/limits always shows the ones in force. Messages from support count against none of your limits, and a reply that reopens a closed ticket also counts against open.

A reached limit answers 409 SUPPORT_QUOTA_REACHED, and nothing is saved:

{
"statusCode": 409,
"error": "SUPPORT_QUOTA_REACHED",
"message": "A support limit for this account was reached.",
"data": { "limit": "tickets_day", "tier": "free", "retry_after_s": 3600 }
}

limit names the row, tier your tier, and retry_after_s the seconds until the limit frees itself. retry_after_s is present for tickets_day, tickets_30d and messages_day. open frees when you close a ticket, and retained when old closed tickets are deleted.

Request limits apply on top of support limits. A request over one answers 429 RATE_LIMIT_EXCEEDED with Retry-After.

LimitDefault
Reads per account600 a minute
Writes per account120 an hour
New tickets per address60 an hour
Writes per address1,200 an hour

Requests from the public IPv4 address of a Hoody server automatically get higher per-address limits on opening tickets and on writes. Account limits are unchanged. A lookup by client_key costs one read against your read limit, uses no ticket or message limit, and never marks a ticket read.

Two refusals concern the whole platform rather than your account. In both, nothing was saved, and reading and closing tickets keep working.

AnswerMeaning
503 SUPPORT_BUSYSupport reached its daily volume for all accounts. Retry-After gives the seconds to the next UTC midnight
503 SUPPORT_STORAGE_FULLSupport cannot store new tickets or messages right now
ItemBehaviour
BatchingSeveral replies on one ticket can share one notification, and you get at most one per ticket every 10 minutes
support_reply_emailOn your user record. GET /api/v1/users/me shows the value in force (true unless you turned it off)
support_reply_email_storedWhether you made a choice
Change itPUT or PATCH /api/v1/users/{id}, from a signed-in session
ItemRule
next_sinceOpaque and belongs to your account. Store it as it is; never build or edit it, and never use another account’s. When nothing of yours changed, the same value comes back
Browse instead of waitGET /api/v1/support/tickets lists your tickets one page at a time, with an optional status filter; pass next_cursor back as cursor until it is null
Thread pagingMessages newest first, 50 at a time. Reading the latest page also marks the ticket read. When has_older is true, pass the smallest seq you have as before_seq to get older messages

How client_key works is on the guide.

ItemRule
ScopeKeys of tickets are scoped to your account, and keys of replies to you and one ticket, so use a new key for each new ticket or message
CLI rerun linePrinted with the key after an unknown outcome. For 503 SUPPORT_BUSY and SUPPORT_STORAGE_FULL the CLI prints no such line, because nothing was saved
Ticket lookupAnswers with the ticket and its first message
Reply lookupAnswers with the message and the ticket, and matches only your own replies on that ticket
Ticket in a lookupComes back as it is now, so its status and unread can differ from the answer you lost
client_key in the queryExactly as the write sent it, URL-encoded (+, &, #, % and any non-ASCII character)
Retry after 404 SUPPORT_KEY_NOT_FOUNDNo saved write carries that key yet. Send the write again with the same body and client_key: if the first one was saved and is still kept, the retry returns it with replayed: true and creates no copy

409 SUPPORT_DUPLICATE means your submission matches text saved less than 60 seconds ago after text cleaning, under another client_key or none. It was not saved again and no account limit was spent. The request rate limits still count the request.

WriteCounts as the same when
New ticketIts subject, category and first message match one of your tickets that is not closed
ReplyIt matches the ticket’s latest message, that message is yours, and the ticket is not closed or is closed for good. A support reply in between means the repeated text is a new message

data names the saved copy in ticket_id and message_id, and retry_after_s says when the same text stops being refused as a duplicate; another refusal, such as a full ticket, can still apply. Read the saved copy instead of sending it again. To retry a write whose answer was lost, send it with its original client_key.

Who reads tickets is on the guide.

ItemRule
Server logsYour ticket text is never written to server logs
Closed ticketsCount toward retained until retention deletes them, by default two years after they were closed. Closing a ticket does not delete it
Never deleted by retentionOpen tickets, tickets waiting for you and tickets that can still be reopened
Symptom, status or messageCauseWhat to do
403The auth token lacks resources.support or is limited to realms, or the request came through a realm host, HTTP Basic or an impersonated sessionAdd the permission, use an account-wide token, and call https://api.hoody.com
403 SUPPORT_NOT_FOR_ACCOUNT or STAFF_ACCOUNT_SCOPE, or 401 STAFF_JWT_REQUIRED for a tokenA staff, admin or platform account, which cannot use support ticketsUse a member account
400 SUPPORT_FIELD_INVALIDA field is missing or has the wrong type, or the request has a field the endpoint does not take. data.field names the field. An unknown field is reported by its position (data.position), never by its nameCompare your keys with the API reference
400 SUPPORT_TEXT_INVALIDA text rule failed. at: "cleaned" means the problem remains after cleaning, for example a message still over 4,000 charactersRead data.rule and data.index and fix the text at that offset; Accepted text explains each rule
404 SUPPORT_TICKET_NOT_FOUNDNo ticket with this id belongs to your account. A malformed id answers the same wayFind your ticket ids with GET /api/v1/support/tickets
404 SUPPORT_KEY_NOT_FOUNDThe outcome of the write is unknown, not refusedRead again later, or resend the write with the same body and client_key, as in Safe retries
409 SUPPORT_QUOTA_REACHEDA support limit was reached; data.limit names itFor open, close tickets that are solved; open counts tickets waiting for support and tickets waiting for you. For the daily and 30-day rows, wait data.retry_after_s seconds
409 SUPPORT_TICKET_LIMITYou sent the 50 messages one ticket allowsOpen a new ticket; the old one stays readable
409 SUPPORT_TICKET_FULLThe ticket reached its size limit and is closed for goodOpen a new ticket; the old one stays readable
409 SUPPORT_TICKET_EXPIREDThe ticket was closed more than 30 days agoOpen a new ticket; the old one stays readable
409 SUPPORT_IDEMPOTENCY_CONFLICTThis client_key was already used with a different bodyUse a new key for a new ticket or message, or resend the original body exactly to get the first result back
409 SUPPORT_DUPLICATEYour submission matches text saved less than 60 seconds ago after text cleaningRead the saved copy; see Duplicate text
422 INVALID_CURSORThe since or cursor value is not accepted, for example after a service restore or an API updateFor an invalid since, call changes without since and save next_since, then list all your tickets, following next_cursor, and read each unread ticket. Continue polling from the saved position. For an invalid listing cursor, repeat GET /api/v1/support/tickets without cursor, with the status filter you want
429 RATE_LIMIT_EXCEEDEDToo many requests in a short timeWait for the seconds in Retry-After, and poll no more often than every 60 seconds
503 SUPPORT_BUSYSupport reached its daily volume; the write was refused without saving anythingWait for the next UTC midnight, given in Retry-After
503 SUPPORT_STORAGE_FULLNew tickets and messages are blocked; nothing was savedWait; reads and closing keep working
503 SUPPORT_UNAVAILABLESupport is temporarily down, and a write that got this answer may or may not have been savedLook it up by its client_key, or send it again with the same key and body after a few minutes