Batch Send FeatureGame Operator Card
Send FEATURE GAME card to specified Player, supports sending to multiple Players and multiple Games at once
Note: FEATURE GAME Cards: Regular Feature Games Card, Powerful Feature Games Card, Super Powerful Feature Games Card
API Information
- URL：
POST /v2/items/usesimplefeaturegame/batch - Authentication：Bearer Token
- Encryption：Requests are encrypted using AES-256-GCM; responses are returned as plaintext JSON
request
Request Headers
POST /v2/items/use HTTP/1.1
Host: api.example.com
Content-Type: application/json
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
x-agentid: integratorNBTest04
x-timestamp: 1769746894501
x-nonce: 56ffd5ecd8a3a4457863a0bd7c298fb2
x-signature: 904e97bee2589b93e9747eed0346c68b23d8ff8b568dabaf4b94a5e89093df67
Request Parameters
Decrypted Request
{
"cipherText": "G0ZMDELeJwx+7JcIfIFOLJjkSzANPu6krGM2uw==..."
}
Parameters Before Encryption
{
"usernames": ["alice01", "bob02"],
"gameCodes": ["VP_240001_1", "VP_240002_1"],
"spinIds": [
"fg_alice_g1_0001",
"fg_alice_g2_0002",
"fg_bob_g1_0003",
"fg_bob_g2_0004"
],
"cardType": 11,
"itemBet": 50,
"maxWinAmount": 3000,
"expiredTime": "2026-04-30T12:00:00.000Z"
}
| Field | Type | Required | Description |
|---|---|---|---|
usernames | string Array | Yes | Player Account |
gameCodes | string Array | Yes | Game Code |
spinIds | string Array | No | Operator Card Unique Identifier, automatically generated by the system if not provided |
cardType | number | Yes | Card Type, available parameters 11, 21, 22 |
itemBet | number | No | Operator Card Bet Amount, can be filled according to BetList. If not filled, the smallest Bet will be used by default. |
maxWinAmount | number | No | Maximum winning amount |
expiredTime | string | No | Card expiration time |
Response
Success Response
{
"code": 0,
"message": "No error.",
"data": {
"successList": [
{
"username": "alice01",
"gameCode": "VP_230001_1",
"spinId": "spin_alice_g1_0001",
"code": 0,
"message": "No error.",
"itemId": "generated-item-id1"
},
{
"username": "alice01",
"gameCode": "VP_230003_1",
"spinId": "spin_alice_g1_0001",
"code": 0,
"message": "No error.",
"itemId": "generated-item-id2"
}
],
"failedList": [
{
"username": "bob02",
"gameCode": "VP_230001_1",
"spinId": "spin_bob_g2_0004",
"code": 8,
"message": "The User is not exist"
},
{
"username": "bob02",
"gameCode": "VP_230003_1",
"spinId": "spin_bob_g2_0004",
"code": 8,
"message": "The User is not exist"
}
]
},
"logUUID": "c6a85c7b-6108-4c88-95fb-fd79a1bda0a1"
}
| Field | Type | Description |
|---|---|---|
code | number | Response code, 0 means Success |
message | string | Response message |
data.successList | Object Array | Item sent Success list |
data.failedList | Object Array | Item sent failed list |
logUUID | string | Request tracking ID for troubleshooting and log queries |
- Item send list parameter Description
| Field | Type | Description |
|---|---|---|
username | number | Player Account |
gameCode | string | Game Code |
spinId | string | Operator Card Unique Identifier |
code | number | Item sending result response code |
message | string | Item sending result response message |
itemId | string | System Operator Card ID, generated only in the Item Success send list |
Error Response
Error Codes
| Code | Description | Handling Suggestion |
|---|---|---|
| 5 | Game is not found | Games not found, delisted, or currency not supported, please confirm gameCode is correct |
| 8 | The User is not exist | Player does not exist, please create Player first |
| 78 | Operator card spinId was used | Please change spinId, if you have questions, contact Customer Support |
| 86 | Game is restricted | Please refer to the Game List document or inquire Customer Support |
| 87 | Invalid item parameter value | Reconfirm parameter rules or Contact Customer Support Team |
| 88 | Only one item can be active at a time in the same game | Player currently has another card active in the Games that has not been used yet |
| 89 | The item has not been used yet, or the spinId does not exist | Reconfirm if Item has been used or if Item has expired and does not exist |
Error Response Example
spinId count does not match Item combination
{
"code": 11,
"message": "spinIds length must match usernames x gameCodes combinations",
"logUUID": "2b82cfaf-d6ad-48fa-9963-4d91639b9b31"
}
Important Notes
- spinId uniqueness: Each spinId must be unique and cannot be reused
- spinId completeness: If spinId is provided, it must match the quantity of "Player Account" x "Game Code", otherwise an error will be Triggered
- Immediate effect: Every FEATURE GAME card sent successfully by this API takes immediate effect
- Partial sending: This batch of Items will not fail to send entirely due to some Items failing to send successfully
Common QA
Q1: Does the API sending FEATURE GAME have an expiration time?
A: After sending, if Player has not logged into Games to use it, it will automatically Settlement after 12 hours.
Q2: Can the API sending FEATURE GAME be cancelled?
A: Yes, it can be cancelled via the Cancel Operator Card API, but it must be done before Player enters Games to use it or before automatic Settlement, otherwise it cannot be cancelled.
Q3: Will the Player be notified after automatic Settlement?
A: When Player logs into Games, a reminder reward message will be displayed, but the animation will not be re-shown. If multiple records are Settlement, only the last Settlement record will be displayed.
Q4: If the expiration time is reached, will the Operator Card automatically Settlement or be cancelled?
A: It will be cancelled, and the Operator Card spinId cannot be reused. There will be no record of this in the backend or bet logs.
Q5: If Player leaves Games during the Games animation, will FEATURE GAME automatically Settlement?
A: Automatically Settle.
Q6: What is the interaction logic between Card expiration time "expiredTime" and automatic Settlement?
A: Automatic Settlement is fixed at 12 hours later. Therefore, if the Card expiration time parameter is set to less than 12 hours, it will first Trigger automatic Settlement. If the CardCard expiration time is set to more than 12 hours from the current send time, it will be fixed at 12 hours to avoid Player experience discrepancy.
Q6: What is the interaction logic between Card expiration time "expiredTime" and automatic Settlement?
A: Automatic Settlement is fixed to 12 hours later. Therefore, if the Card expiration time parameter is set to less than 12 hours, automatic Settlement will be Triggered first. If the Card expiration time is set to more than 12 hours from the sending time, it will be fixed at 12 hours to avoid Player experience discrepancy.