Admin

Admin Website Guide

Operational guide for managing reseller users, wallet balance, API access, products, and SmileOne readiness.

Overview

User approvals

Approve or reject new reseller accounts before they can use protected API endpoints.

Wallet control

Credit or debit BR/PHP wallet balances, then review history for audit checks.

Product updates

Edit product JSON files for package name, SmileOne product IDs, region, and price.

Service health

Check API health, docs status, and SmileOne cookie readiness before accepting orders.

Users

  1. Review pending reseller requests.
  2. Approve valid users; reject unknown or duplicate accounts.
  3. Use user detail view to check ID, wallet, status, and history.
  4. Delete a user only when you are sure the wallet, history, and API key data can be removed.

Wallets

Wallet balance is separated by region. BR balance pays BR products, PHP balance pays PHP products.

Credit example:
User ID : 7829183790
Amount  : 100
Region  : BR

Debit example:
User ID : 7829183790
Amount  : 50
Region  : PHP

Products

Edit these files when package IDs, prices, or product names change:

Product format

{
  "name": "86",
  "products": ["13"],
  "country": "br",
  "price": 61.5
}

For Where Winds Meet, id is also accepted and is converted to the internal product ID list.

API Keys

Issue API keys only to approved reseller accounts. Rotate a key if it is exposed or used by the wrong website.

Authorization: Bearer USER_API_KEY

User-facing documentation is available at /docs.

Operations

Health checks

GET /api/v1/health
GET /api/v1/smileone/status
GET /docs

Deploy checklist

  1. Validate JSON files before upload.
  2. Upload changed product/docs/source files.
  3. Restart service and confirm /api/v1/health returns ok: true.
  4. Open /docs and /admin to confirm website pages load.