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

Once your account has an activated plan purchase paid at least partly by card or crypto, you can share a referral link or a code of your own. When people who sign up through it pay for servers by card or crypto, you earn a share of that spend as Referral credit: a third wallet balance that pays for servers.

  1. Check your status

    GET /api/v1/referrals/me

    eligible: true, enrolment_open: true and enrolled: false mean you can join now.

  2. Join

    POST /api/v1/referrals/me

    The answer is 201 with the same status as GET, now including a random code such as k7m2q9xa and its referral link.

  3. Share the link

    Each active code in codes has a link to the Hoody website with your code in it:

    https://hoody.com/r/k7m2q9xa

    To send people to a particular page, add its path after the code: https://hoody.com/r/k7m2q9xa/pricing opens the pricing page. Capital letters in the code are fine. Adding ?ref=k7m2q9xa to any Hoody page address works too.

Joining, checking code availability and changing codes need your signed-in session, also in the SDK and CLI (hoody referrals); auth tokens receive 403 for those operations. Reading your status with GET /api/v1/referrals/me also accepts an account-wide auth token with financial.wallet.read.

In the Hub, open Referrals under Account in the sidebar (or Earn · Affiliates in the account menu), press Join…, then Join. Copy link copies the link of your main code. The same page shows your Referral credit, level and the people you invited. It needs your signed-in session too.

The qualifying purchase is a paid subserver or bare-metal rental you bought, activated and paid at least partly by card or crypto. One paid entirely with credit, or fully refunded, does not qualify. You do not need to keep buying plans to stay eligible.

Right after activation, eligible can take a while to turn true; until then, joining returns AFFILIATE_NOT_ELIGIBLE. While new enrolment is paused, enrolment_open is false and joining returns 409 AFFILIATE_ENROLMENT_PAUSED; members keep their codes and keep earning. Refunds and disputes can withdraw eligibility (eligibility rules).

Joining gives you one random code, which cannot be released. Add vanity codes, such as alex-builds, that are easy to remember or read aloud: up to 3 active at a time and 10 in your account’s life (code rules).

In the Hub, type the code in New code under Your own codes on the Referrals page; it tells you as you type whether the code is available. Press Create to make it.

Through the API, checking a code does not reserve it:

GET /api/v1/referrals/me/codes/check?code=alex-builds

Then create it. The answer is 201 with data: { code, kind, state, link }.

POST /api/v1/referrals/me/codes
{
"code": "alex-builds"
}

Release a vanity code you no longer want. In the Hub, press Retire… next to it, then Retire code. Through the API, the answer is 200 with data: { code, released: true }.

DELETE /api/v1/referrals/me/codes/alex-builds

Only a new account gets a referrer, when it is created; an existing account cannot get one later.

WayWhat happens
Through your linkWhile signed out, the browser remembers the first referral code for up to 7 days or until sign-in, and fills the signup page’s Referral code (optional) field. Later links do not replace an unexpired remembered code
By typing the codeThe person selects Have a referral code? if the field is hidden, then enters the code in Referral code (optional); it replaces any code remembered from a link

GitHub and Google sign-up from that page keep the code too. An unknown, blocked or released code does not stop the signup; the account has no referrer. The person who signs up gets no reward of their own, and self-referrals earn no Referral credit (signup capture).

LevelConditionYour share
ReferrerYou joined the program5%
Creator11 or more referred customers who earned you credit that has not been fully reversed10%

Creator applies to a UTC calendar month when at least 11 different customers earned you credit before it began. A customer counts while any of that credit is not fully reversed (level rules).

You earn on the card or crypto part of a referred customer’s server purchases, after any refund: paid subservers with renewals, and bare-metal rentals and reservations once delivered. Hoody AI, setup fees and any part paid with promotional, bonus or Referral credit earn nothing (details).

A customer’s first qualifying server purchase must be ordered within 90 days of signup; delivery can happen later. The customer then earns for you for 12 months from activation of that purchase, with bare-metal service earning only within their first 3 calendar months of bare-metal service (earning window). You earn on the customers you bring, not on the people they bring.

Credit from each purchase has a 60-day hold from when the server purchase is activated. It becomes due at the first 00:00 UTC at or after the end of its hold, and all your credit due by then is released together. next_release_at shows the next release day; processing or a review can delay the release itself. A refund reduces or reverses the credit, and a disputed payment keeps it on hold during review (holds and reversals).

Referral credit pays for paid subservers, bare-metal rentals and their renewals, including a rental’s one-time setup fee, and is spent first, before your General Balance. Available credit does not expire. It cannot pay for Hoody AI, go to another account or move to the AI Balance, and selling or trading it is not allowed.

Creators can also take available credit out as money, by bank transfer or crypto in some cases; credit on hold cannot be withdrawn. Withdrawal is off by default on every account, including when you reach Creator: ask Hoody support, who validates each request.

Credit reversed after you spent it comes from your Referral credit and then from future referral earnings (referral_credit_owed), never from money you paid in. Deleting your account discards your Referral credit and forfeits credit on hold. See the balance rules.

GET /api/v1/referrals/me returns your codes, level, counts and credit totals. You see no referred person’s name, email address, account ID, or signup or purchase lists, and the counts do not guarantee anonymity (privacy). Counts show as "0", "fewer_than_3", or an exact number from 3 upward. See the status fields.

  • Sign up over the API: an email signup sends the code as referral_code, a browser GitHub or Google sign-in as ref (signup capture).
  • Read with an auth token or MCP: an auth token with financial.wallet.read, or an MCP agent, can read your status, not join or change codes (access and limits).
  • Monthly earnings: monthly splits earned and reversed credit by UTC month for 12 months (status fields).
  • Refunds and your history: a refunded part returns to the balance that paid it. Your history shows “Referral reward” and “Referral reward reversal”, and an invoice a “Referral credit” line; see the balance rules.
  • Program review: Hoody may hold or reverse credit, remove codes, end participation or change the program. If removed, your codes stop bringing signups and held credit waits (program changes).
  • Rate limits: over the per-account limit you get 429; wait the Retry-After seconds (access and limits).

See the Referral Program reference.