Query qiyaov Referral Reward Information

qiyaov currently does not have an aggregated /api/v1/distribution/ endpoint. Referral reward data consists of four groups of APIs: status, history, level, and redemption; please call the required resources as needed and avoid relying on a non-existent summary response.

Preparation

  1. Create and save an Account Token in the Account Token Console.
  2. Use GET /api/v1/platform-tokens/me/ to obtain the current account UUID.
export PLATFORM_TOKEN='your account token'
export USER_ID='your account UUID'

Available APIs

Method URL Purpose
GET /api/v1/distribution-statuses/?user_id=${USER_ID} Current account's cumulative referral amount, rewards, and level
POST /api/v1/distribution-statuses/initialize/ Initialize or refresh the current account level for the first time; writes data
GET /api/v1/distribution-histories/?user_id=${USER_ID} Referral reward history
GET /api/v1/distribution-levels/ Level and rate rules
GET /api/v1/distribution-redemptions/preview/ Preview currently redeemable rewards; optional amount
GET /api/v1/distribution-redemptions/ Completed redemption records
POST /api/v1/distribution-redemptions/redeem/ Confirm redemption; requires idempotency_key and creates an irreversible redemption

Read-Only Request Examples

curl --get 'https://api17.platform.acedata.cloud/api/v1/distribution-statuses/' \
  --data-urlencode "user_id=${USER_ID}" \
  -H "Authorization: Bearer ${PLATFORM_TOKEN}"

curl --get 'https://api17.platform.acedata.cloud/api/v1/distribution-histories/' \
  --data-urlencode "user_id=${USER_ID}" \
  --data-urlencode 'limit=100' \
  -H "Authorization: Bearer ${PLATFORM_TOKEN}"

curl 'https://api17.platform.acedata.cloud/api/v1/distribution-levels/' \
  -H "Authorization: Bearer ${PLATFORM_TOKEN}"

curl 'https://api17.platform.acedata.cloud/api/v1/distribution-redemptions/preview/' \
  -H "Authorization: Bearer ${PLATFORM_TOKEN}"

The response format verified online is:

  • status, history, level, redemption list: {count, items};
  • redemption preview: a single object containing fields such as eligible, reason, reward_amount, credit_amount, credits_per_usd, currency, package, and global_application.

Status items and history items may be extended based on referral risk control, compensation, and reward rules; clients should read them as needed and should not rely on aggregated fields such as referral_url, recent_orders, and withdrawable_balance that are not returned by the APIs in older documentation.

Initialization and redemption are both write operations. Production scripts should first call read-only APIs to check the status and persist a unique idempotency_key for redemption requests; do not automatically retry redemptions with unknown results.