Transfer Wallet
Handles wallet operations for users, including depositing and withdrawing funds. These actions are processed securely based on the provided user information and transaction details. The API validates
Headers:
X-Transaction-Id(GUID) is required for idempotency control.Player token should be provided either in
X-Player-TokenandAuthorization: Bearer <token>for token service. Idempotency: identical retried requests return the same result; conflicting retried requests return 409. This endpoint does not return the updated balance.
REQUIRED - JWT Authorization header using the Bearer scheme. All API endpoints require authentication, except for authentication endpoints (Connect/authentication). Example: "Authorization: Bearer {token}"
Unique transaction identifier for request tracking
2f6fc9e6-989f-48ef-9f93-1c8d2102d5c6Player access token for session validation
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Withdraw processed. Use /wallet/player/balance to get the updated balance.
No content
Invalid request or processing error.
Invalid or expired player session.
Idempotency conflict: same X-Transaction-Id with different request body.
No content
Scope and Limitations
Header X-Transaction-Id (GUID) is required for idempotency control. Identical retried requests should return the same result; conflicting retries will return 409. This endpoint does not return the updated balance.
REQUIRED - JWT Authorization header using the Bearer scheme. All API endpoints require authentication, except for authentication endpoints (Connect/authentication). Example: "Authorization: Bearer {token}"
Unique transaction identifier for request tracking
14d67a8e-4ece-4c88-801f-41462a4c9f8dPlayer access token for session validation
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Deposit processed. Use /wallet/player/balance to get the updated balance.
No content
Invalid request or processing error.
Idempotency conflict when X-Transaction-Id is reused with different body.
No content
Last updated