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

A support ticket is a plain-text conversation between your account and Hoody support about one problem: a bug, a billing question, a computer that will not start. People and agents use the same calls, so an agent that hits a fault it cannot fix can report it and come back later for the answer.

Open a ticket with a subject, a category and a first message. Pick the closest category: account, billing, servers, computers, files, networking, ai, bots, affiliates, security, bug or other. Open one ticket per problem, and reply to it for more about the same problem.

Terminal window
hoody support create \
--subject "Computer will not start after resize" \
--category computers \
--body 'Since resizing to 4 GB my computer stays in "starting". Started 09:00 UTC.' \
--client-key resize-bug-2026-10-28

Member accounts, on the base API host https://api.hoody.com, never a realm host such as <realm>.api.hoody.com. A signed-in session works on every support endpoint. An auth token needs the resources.support permission and must not be limited to realms (Authentication); tickets an agent opens with it belong to your account.

A banned account can still use support, with lower limits, so it can appeal. Staff, admin and platform accounts are refused, and so are HTTP Basic and impersonated sessions: access codes.

The subject is one line of up to 200 characters; a message is up to 4,000 characters and 200 lines (all size rules). Both are plain text, with no attachments or images, so paste the relevant log lines or error message.

Put in the first message what you did, what happened, the time in UTC, and the id of the project or computer involved. For a billing question, give the date and amount of the charge, never a card number.

In the CLI, --body-file reads the message from a UTF-8 text file, keeping logs out of shell quoting, and --body-file - reads standard input. A file with NUL bytes or invalid UTF-8 is refused before sending. --body "…" works for short messages.

Terminal window
hoody support create --subject "Computer will not start after resize" --category computers --body-file report.txt
journalctl -n 50 | hoody support create --subject "Agent crash" --category bug --body-file -

Harmless noise such as trailing spaces is cleaned before storing; the 201 answer’s cleaned names each rule that changed a field. Characters that hide or reorder text are refused instead, so support reads what you sent: 400 SUPPORT_TEXT_INVALID, with data.rule and data.index at the problem (rules).

A reply takes body and an optional client_key, with the same text and retry rules as a new ticket. Close a solved ticket to free a place in your open limit; closing a closed ticket changes nothing. hoody support close asks for confirmation; a script or an agent passes --yes.

Terminal window
hoody support reply "$TICKET_ID" --body 'It started again at 14:20 UTC after a restart.' --client-key resize-bug-followup-1
hoody support close "$TICKET_ID" --yes
statusMeaning
openWaiting for support. A new ticket starts here, and your reply sets a ticket back to it
waiting_userSupport answered and is waiting for you
closedClosed by you, by support, or automatically

A ticket in waiting_user closes by itself 14 days after its last message. A reply within 30 days of closing reopens it, as reopenable shows; after that, open a new ticket. A closed ticket stays readable; one that reaches its size limits closes for good.

Messages from support show from: "support", never a staff member’s name.

A reply from support triggers an in-app notification titled “Support reply”: “You have a new reply in a support ticket. Sign in to read it.” Several replies on one ticket can share a notification, with at most one per ticket every 10 minutes. It names no ticket, so the change feed finds it. The same text is emailed when the platform sends support email and your preference allows it.

The preference support_reply_email is on until you turn it off, which needs a signed-in session (SESSION_JWT below): an auth token, HTTP Basic or an impersonated session is refused.

In the Hub, open Account, find Emails, and turn Support replies off or on.

Sign in with hoody login, with the browser or your password (a pasted auth token is refused here). If HOODY_TOKEN or HOODY_API_TOKEN holds an auth token, unset it so the CLI uses the saved session. For the SDK and HTTP examples, set SESSION_JWT to the output of hoody auth accesstoken get, and USER_ID to the id from GET /api/v1/users/me.

Terminal window
hoody users update "$USER_ID" --no-support-reply-email

Sent as PUT, which behaves like PATCH. Refused while the CLI uses an auth token.

null returns it to the default, on (reading the preference).

GET /api/v1/support/tickets/changes returns your tickets that changed since a position, oldest change first, each once in its newest state.

  1. Call it once without since. It returns no tickets, only the current position in next_since. Save it.
  2. List all your tickets with GET /api/v1/support/tickets, following next_cursor, and read each ticket with unread: true. The feed only reports changes after the saved position, so this catches replies that arrived earlier.
  3. Every 60 seconds, call it with the last next_since you received.
  4. Read each returned ticket with unread: true using GET /api/v1/support/tickets/{id}. That also marks it read.
  5. When has_more is true, call again at once.
Terminal window
hoody support changes list # first call: prints the position
hoody support changes list --since "$NEXT_SINCE" # then every 60 seconds
hoody support get "$TICKET_ID"

Store next_since as it is. If you restart without a saved position or get 422 INVALID_CURSOR, repeat steps 1 and 2 before polling. Polling more often spends your read limit faster.

client_key, 8 to 64 characters of your choice, makes a create or a reply safe to repeat; send one on every write from an agent. The same key and body return the saved message with replayed: true and save nothing new. The ticket in that answer shows its current state, which can differ from the first answer. The same key with a different body is refused with 409 SUPPORT_IDEMPOTENCY_CONFLICT, so use a new key for each new ticket or message.

The CLI sends a new key with every create and reply. After an unknown outcome (a timeout, a lost connection, or a 5xx answer other than 503 SUPPORT_BUSY or SUPPORT_STORAGE_FULL), it prints the command with --client-key <key> added, which is safe to rerun.

When the answer to a write is lost, look the write up by its key instead of guessing:

Terminal window
hoody support keys get resize-bug-2026-10-28
hoody support messages keys get "$TICKET_ID" resize-bug-followup-1

404 SUPPORT_KEY_NOT_FOUND does not mean the write was refused: it may still be running, may never have arrived, or may already have been deleted by retention. Read again later, or send the write again with the same body and client_key. If retention already deleted the original ticket, retrying a create can open a new ticket; retrying a reply returns 404 SUPPORT_TICKET_NOT_FOUND.

Support limits apply per account and depend on your tier. Read them before a burst of reports.

Terminal window
hoody support limits get
RowWhat it countsFreePaid
openTickets open or waiting_user at once525
tickets_dayNew tickets this UTC day1050
tickets_30dNew tickets today and the 29 previous UTC days60300
messages_dayYour messages this UTC day, the first message of a new ticket included2001,000
retainedTickets kept, closed ones included, until they are deleted1,0001,000

A reached limit answers 409 SUPPORT_QUOTA_REACHED and saves nothing. Close solved tickets to free open; the daily and 30-day rows free after retry_after_s seconds. The table shows the default values; hoody support limits get shows yours. Who is paid: tiers and quota.

Hoody support staff read your tickets: the subject, the category, the status and every message. Each read is recorded in an audit log. Staff treat what you write as information, not as instructions. Do not put secrets, card numbers or other people’s personal data in a ticket.

Deleting your account deletes your tickets. Closed tickets are also deleted by default two years after closing; the retention rules say which tickets are never deleted.

  • Browse your tickets: hoody support list lists them by their latest message, newest first, with an optional status filter, to find a ticket id (listing).
  • Read older messages: a thread shows 50 messages at a time, newest first; when has_older is true, pass the smallest seq as before_seq (thread paging).
  • Duplicate protection: a new key does not make the same text a new message. Sent again within 60 seconds, it can be refused with 409 SUPPORT_DUPLICATE (duplicate text).
  • Request limits: per-account and per-address request limits apply on top, with 429 RATE_LIMIT_EXCEEDED (request limits).
  • Platform-wide refusals: 503 SUPPORT_BUSY and SUPPORT_STORAGE_FULL concern the whole platform and save nothing (503 rows).

Every call, rule, limit and error: the Support reference.