Send Props for Pre-registration Reward Code
Description
Request the vendor API to send props to a player role.
This interface is used for prop delivery across all game payment channels.
The basic parameters include: item type (elementType), item ID (elementId), item count (count), platform user ID (userId), mail title (title), mail content (content), server code (serverCode), current timestamp (timeStamp), and MD5 signature (sign).
The domain name is determined by agreement between the vendor and the product team. The KEY value used in the sign signature can be provided by the vendor (e.g., 8–32 characters consisting of uppercase and lowercase letters or digits, with no special characters).
Processing Flow
Request URL: must support both POST and GET. POST is recommended. Default content type: application/x-www-form-urlencoded.
Domain path, provided by the vendor, for example: http://xxx.xxx.com/user/sendProps
Test server link:
http://xxx.xxx.com/user/sendProps?elementType=1&elementId=0&userId=3258506&count=1&serverCode=ld4&timeStamp=1378456412008&roleId=12045897&sign=1faec808b862af2d5a726f993477529b&title=abc&content=12334Note:
Pre-registration prop delivery uses the same interface as Send Props API (Optional).
It can be understood as sending a pre-agreed reward code for pre-registration rewards.Request Parameters
| Parameter | Description | Required |
|---|---|---|
| serverCode | Server CODE | Required |
| userId | User ID | Required |
| elementType | Pre-registration item type agreed by both parties, for example: 0 | Required |
| elementId | Pre-registration reward ID agreed by both parties, for example: 99999 | Required |
| count | Pre-registration item count agreed by both parties, for example: 1 | Required |
| timeStamp | Timestamp, accurate to seconds | Required |
| sign | MD5 signature: MD5(serverCode + userId + elementType + elementId + count + activity KEY + timeStamp); the activity KEY must consist of 8–32 uppercase or lowercase letters or digits, with no special characters | Required |
| title | Pre-registration mail title agreed by both parties | Optional |
| content | Pre-registration mail content agreed by both parties | Optional |
| roleId | Role ID | Optional |
Response Result
| Result | Example | Description |
|---|---|---|
| Success | {"ret":0, "msg":"ok"} | ret:0 means received successfully |
| Failure | {"ret":1001, "msg":"Parameter error"} | Non-zero ret indicates an error. If custom error codes are defined, provide the code description. |
Response JSON Fields
| Parameter | Description | Required |
|---|---|---|
| ret | Return status | Required |
| msg | Return message | Required |
Error Codes
1001 Parameter error 1002 User does not exist 1003 Sign error 1004 Duplicate submission 1008 Account disabled 65535 Server error