Report Rewarded Video Completion
This API must be called on the server side. Never call it directly from the frontend (APP client, web page, mini game, etc.) to avoid the risk of credential leakage.
API Description
API English name ad.rewardNotify
Description After the APP server determines that a user has triggered the rewarded video completion event, it calls this API to report the data to SUD OP SVR. SUD OP then completes the verification and notifies the Game SVR to grant the reward.
Note: This API requires secondary encryption and signing of server-to-server communication: request parameters must be encrypted and signed, and responses must be signature-verified and decrypted. This effectively prevents data tampering and leakage.
Call Method
HTTPS Call
POST /v1/ad/reward/notify?access_token=ACCESS_TOKENPrepend the base URL for your application's service region to the API path. See Service Regions and API Addresses.
Request Parameters - Query
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| access_token | string | Yes | API call credential |
Request Parameters - Body
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| sud_transaction_id | string | Yes | Passed through by SUD OP via setServerSideVerificationData; the APP server retrieves it as-is from the SSV callback | |
| transaction_id | string | Yes | Transaction ID issued by the APP platform, used for idempotent deduplication |
Return Value
The returned JSON data packet
| Field | Type | Description |
|---|---|---|
| errcode | int32 | Error code |
| errmsg | string | Error message |
| is_valid | boolean | true: report succeeded, SUD OP has accepted it and initiated the reward-granting flow; false: report failed (e.g. sud_transaction_id does not exist or has already been processed) |
Call Example
Note: The request example below shows the business data before encryption; what is actually sent is the ciphertext with signature headers, and the response example shows the business data after signature verification and decryption. See Server API Signature and Encryption for the packaging and signing rules.
Request Data Example
{
"sud_transaction_id": "2026042403100000000000001007",
"transaction_id": "tx_abc123"
}Response Data Example
{
"errcode": 0,
"errmsg": "success",
"is_valid": true
}