Account — partner program

The dealer Partner Program (affiliate landing) loads program ranks, rules, showcase content, and the user’s application state. Users submit a Join form via action_type=apply.

Use your registration domain in every form body — not the API hostname.

Playground & Profile

Playground — Home feed → Platform → Partner program when running npm run docs:stack. Profile → Account can load a status preview when signed in.

Application status

Prefer application?.status (e.g. pending) over can_join alone when the UI shows “Awaiting review”.

Integrator scope

In scope for your app: load the program landing (action_type=status) and submit the Join form (action_type=apply). Reflect application?.status (e.g. pending) in the UI. Many dealers require email verification before apply — use POST …/auth/send-verify-email and POST …/auth/verify-email (same access_token, domain, email, language EN | VI | TH; verify sends code) when program.partner_verify / application.verify_email indicate the user has not verified yet.

Out of scope: approving or rejecting applications, referral links, commission dashboards, and payouts are dealer/operator workflows — not something integrators control via this API. Do not assume extra action_type values or endpoints until documented from a verified capture.

Status (landing)

POST https://api.gommo.net/api/apps/go-mmo/users/partner_program
Content-Type: application/x-www-form-urlencoded

Field	Required	Notes
access_token	yes	User session token
domain	yes	Registration domain
action_type	yes	status
lang	optional	Locale id, e.g. en
language	optional	e.g. EN, VI
device_id, device_name, device_info	optional	Same as login

Typical success shape (fields vary by dealer):

{
  "success": true,
  "program": { "levels": [], "rules": "", "showcase": [] },
  "application": null,
  "runtime": 0.05
}

When the user has applied, application may include status: "pending" (or other states when verified).

Verified dealer shapes may also include (inside program):

• default_level / levels[] — commission rates (e.g. credit_rate, package_rate, app_rate, agent_rate, level_name)
• rules — string or object with title, intro, items[]
• showcase — array or object with partners[]
• can_join, application, domain_flags

Single status call — typical out of scope for integrators: official referral copy URL, monthly commission/revenue aggregates, settlement/promo lists. Those may exist only on the dealer’s own affiliate UI or undocumented endpoints. The portal Affiliate page reflects status + apply only; empty overview tabs are expected when those fields are absent.

Apply (Join form)

Same URL with action_type=apply.

Field	Required	Notes
bank_name	yes	Payout bank
account_name	yes	Account holder
account_number	yes	Account number
bank_extra	optional	Branch / extra info
contact	yes	Contact channel
email	yes	Email
reason	yes	Why join
accept_rules	yes	Must be 1
access_token, domain	yes
language, device_*	optional

Success (verified capture):

{
  "success": true,
  "message": "…",
  "program": { "application": { "status": "pending" } },
  "runtime": 0.04
}

Mode B (optional gateway)

Operation	Gateway (Bearer + JSON)	Upstream
Status	POST {gateway}/gateway/partner-program with { "action_type": "status" }	…/users/partner_program
Apply	Same path with { "action_type": "apply", … }	Same
Send verify email	POST {gateway}/gateway/partner-program/send-verify-email JSON { "email", "language" } (EN | VI | TH)	…/auth/send-verify-email form: access_token, domain, email, language — no device_*
Verify email code	POST {gateway}/gateway/partner-program/verify-email JSON { "email", "code", "language" }	…/auth/verify-email same base fields + code

Success for send (dealer capture): message, mail_provider (e.g. resend). Gateway returns upstream errors when confirmation fields are missing.

JSON camelCase aliases: bankName, accountName, accountNumber, bankExtra, acceptRules.

OpenAPI: openapi.yaml.

SDK: @ai-gateway/client — auth.getPartnerProgramStatus(), applyPartnerProgram(). See SDK authentication.

→ Creator rewards · Support tickets · Session devices · Change password · Endpoint map · Deploy → Self-host (advanced)