Midasbuy System — API documentation

This value is generated from the current site (protocol, host, and folder). After you upload to your server, open this page again — URLs will match your domain automatically. If your host uses a reverse proxy and links are wrong, set the environment variable PUBLIC_BASE_URL (e.g. https://example.com/myapp). Avoid exposing the client key in public front-end code when possible — prefer a backend that adds the header.

On HTTP 200, the response body is JSON from the upstream service. The gateway does not rewrite it — you get the same structure the provider returns.

• success (boolean) — overall outcome of the business call
• message (string) — short summary (often "Ok" on success)
• data (object) — action-specific payload; always inspect data.status (and messages inside data) for the real result

Success rule: treat the call as fully successful only when the HTTP status is 200 and the parsed JSON has success === true. Any other combination is not successful; show message and any relevant fields inside data.

Real values (timestamps, UC amounts, optional login fields, etc.) depend on the upstream. The examples below are illustrative so you can wire parsers and UI; run your own test calls for exact payloads.

client_ref is required for reconciliation and auditing, especially for activate actions. Send a unique value from your system for every request (for example, your order ID, invoice ID, or UUID). The gateway stores it in the operations log even when the request is blocked, fails quota checks, fails upstream transport, or returns a business error.

The client_ref value is used by this gateway only; it is removed before forwarding the request to the upstream provider.

Request body (JSON):

{"client_ref": "YOUR_UNIQUE_ID", "player_id": 555555555}

Example success response (HTTP 200, illustrative):

{
  "success": true,
  "message": "Ok",
  "data": {
    "status": "success",
    "message": "Player found",
    "player_id": 555555555,
    "player_name": "PlayerName"
  }
}

Request body (JSON):

{"client_ref": "YOUR_UNIQUE_ID", "uc_code": "YOUR_CODE"}

Example success response (HTTP 200, illustrative):

{
  "success": true,
  "message": "Ok",
  "data": {
    "status": "activated",
    "uc_code": "YOUR_CODE",
    "amount": 60,
    "activated_at": 1631817600,
    "activated_to": 555555554
  }
}

Request body (JSON):

{"client_ref": "YOUR_UNIQUE_ID", "player_id": 555555555, "uc_code": "YOUR_CODE"}

Example success response (HTTP 200, illustrative):

{
  "success": true,
  "message": "Ok",
  "data": {
    "status": "success",
    "message": "Code activated",
    "player_id": 555555555,
    "player_name": "PlayerName",
    "code_activated": "YOUR_CODE",
    "activated_at": 1763891643000,
    "activated_to": 555555554,
    "account_login": "login@example.com",
    "account_password": "…"
  }
}

account_login / account_password may be absent depending on provider and product.

Redeem up to 5 codes in one call; each code counts toward the client’s daily quota. Same JSON envelope as other actions; data.results is an array of per-code outcomes. Request example:

{"client_ref": "YOUR_UNIQUE_ID", "player_id": 555555555, "uc_codes": ["CODE1", "CODE2"]}

Full success sample omitted here; shape matches upstream bulk-activate docs when you need it.

If you never get a success sample in real traffic, the response body usually tells you which layer failed:

• Gateway — messages like Invalid API key, X-Api-Key required, Client disabled, Daily operation limit reached, or Upstream request failed (502). Fix client key, admin limits, or server/network to midasbuy-api.com.
• Upstream — HTTP 200 with "success": false, or 4xx/5xx JSON from the provider. Fix player_id, uc_code, or contract with the upstream; ensure the server master API key in config is valid.

Use gateway-test.html or proxy-test.html on the same host with a known-good client key and minimal body (e.g. getPlayer with a real player id) to separate “gateway blocked” from “upstream rejected”.

const url = "https://weecard.almirsystem.cloud/gateway.php?action=getPlayer";
const res = await fetch(url, {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-Api-Key": "YOUR_CLIENT_KEY"
  },
  body: JSON.stringify({ client_ref: "YOUR_UNIQUE_ID", player_id: 555555555 })
});
const data = await res.json();
// On HTTP 200: check data.success, then data.data (and data.data.status when present)

curl -X POST "https://weecard.almirsystem.cloud/gateway.php?action=getPlayer" ^
  -H "Content-Type: application/json" ^
  -H "X-Api-Key: YOUR_CLIENT_KEY" ^
  -d "{\"client_ref\":\"YOUR_UNIQUE_ID\",\"player_id\":555555555}"

On Linux/mac, use \ for line continuation instead of ^.