Skip to main content

Cancel Operator Card

Cancellation is possible before the Player uses it. If the Player has entered the game and triggered the animation, it cannot be cancelled.

API Information

  • URLPOST /v2/items/cancel
  • Authentication:Bearer Token
  • Encryption:Requests are encrypted using AES-256-GCM; responses are returned as plaintext JSON

request

request Headers

POST /v2/items/cancel 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

Parameters Before Encryption

{
"username": "testaccount001",
"spinId": "VPItemTestTrans1015_ghjklhtombg"
}

Encrypted Request Body

{
"cipherText": "G0ZMDELeJwx+7JcIfIFOLJjkSzANPu6krGM2uw==..."
}
FieldTypeRequiredDescription
usernamestringYesPlayer Account
spinIdstringYesOperator Card Unique Identifier

Response

Success Response

{
"code": 0,
"message": "No error.",
"logUUID": "6589bf8d-fe74-48bd-841a-71bf8f848f86"
}

Error Response

Cancellation Completed or Does Not Exist

{
"code": 4,
"message": "The transaction doesn`t exist.",
"logUUID": "6589bf8d-fe74-48bd-841a-71bf8f848f86"
}

Common Error Codes

CodeDescription
4Transaction does not exist or has been cancelled
8Player does not exist
11Parameters error
83Authentication Failed
84Decryption Failed

Important Notes

  1. spinId Uniqueness: Use spinId to identify the Operator Card to be cancelled
  2. Idempotency: Repeated cancellation requests for the same spinId will return the same result
  3. Cancellation Timing: Cancellation must be done before the Operator Card is used. If the Player has entered the game and triggered the animation, it cannot be cancelled