Query Rewarded Video Completion
This is a callback API implemented by the APP server and provided to SUD to call. After SUD OP receives the SSV callback from the ad platform, it uses this API to confirm the user's rewarded video completion status with the APP server.
API Description
API English name ad.rewardQuery
Description Query rewarded video completion. After SUD OP receives the SSV callback from the ad platform, it proactively calls this API to confirm the user's rewarded video completion status with the APP server.
Note: This API requires secondary encryption and signing of server-to-server communication: the callback request must be signature-verified before any business logic runs. This effectively prevents data tampering and leakage.
Call Method
HTTPS Call
POST <APP custom callback URL>Request Parameters - Body
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| sud_transaction_id | string | Yes | Unique order number for this rewarded video completion, generated by SUD OP and passed through in setServerSideVerificationData |
Return Value
The returned JSON data packet
| Field | Type | Description |
|---|---|---|
| errcode | int32 | Error code |
| errmsg | string | Error message |
| transaction_id | string | Completion order number issued by the APP platform |
| status | int32 | Video status, see the enum description below |
Valid Values of errcode
| Value | Description |
|---|---|
| 0 | Request succeeded |
status Enum Description
| Value | Enum Name | Description |
|---|---|---|
| 0 | PROCESSING | Video in progress (not closed, including not started, playing, etc.) |
| 1 | COMPLETED | Completed (video closed and fully played) |
| 2 | INCOMPLETE | Not completed (video closed but not fully played) |
SUD OP triggers the reward-granting flow only when
status = 1 (COMPLETED).
Call Example
Note: The request example below shows the business data after decryption; what actually arrives is ciphertext with signature headers, which must be verified and decrypted before parsing. The response example shows the business data before encryption; the actual response must be encrypted first and the ciphertext then signed. See Callback Signature and Encryption for the full rules.
Request Data Example
{
"sud_transaction_id": "2026042403100000000000001007"
}Response Data Example
{
"errcode": 0,
"errmsg": "success",
"transaction_id": "tx_abc123",
"status": 1
}