Skip to main content

API Documentation Introduction

Welcome to the VP API documentation. This documentation provides complete API specifications for two wallet modes.

👉 Seamless Wallet: View Documentation
👉 Transfer Wallet: View Documentation

General Notes​

Security Requirements​

  1. HTTPS Required

    • All API requests must use HTTPS protocol
    • Ensure SSL certificate is valid and not expired

  2. Encrypted Transmission

    • Sensitive data must use AES-256-GCM encryption
    • Keep encryption keys secure and avoid leakage

  3. Signature Verification

    • Each request must include a valid signature
    • Use SHA256 algorithm for signature verification

  4. Token Management

    • JWT Token is valid for 1 hour
    • Token must be reacquired after expiration
    • Do not pass Token in URL

Request Specifications​

  1. Request Header Settings

    Content-Type: application/json
    Authorization: Bearer {token}

  2. Character Encoding

    • Use UTF-8 encoding uniformly
    • Special characters must be URL encoded

  3. Time Zone Settings

    • All time parameters use UTC+0 timezone
    • Except for x-timestamp in the header which uses millisecond Unix timestamp, all other API time formats must use the ISO 8601 standard YYYY-MM-DDTHH:mm:ss.SSSZ format (e.g.: 2026-02-02T10:30:00.000Z)

  4. Transaction Time Basis

    • Transaction times for Bet Logs and Report queries are all based on txTime (Settlement time)

  5. Player IP Restriction

    • Player IP is not restricted at all during Games, changing IP during Games will not affect gameplay

Error Handling​

  1. Idempotency

    • Use unique "Transaction ID" and "Bet ID" to ensure idempotency
    • Duplicate requests will not result in duplicate deductions

  2. Error Codes

    • For detailed error codes, please refer to the Error Appendix for each wallet mode
    • Seamless Wallet: Error Appendix
    • Transfer Wallet: Error Appendix

Test Environment​

  1. Test Account

    • Please Contact Customer Support Team to obtain a test environment account
    • The test environment is completely isolated from the production environment

  2. Test Key

    • The test environment uses an independent API key
    • The production environment key must be used before going live

  3. Test Data

    • Test environment data will not be synchronized to the production environment

Technical Support​

If you encounter any issues during implementation, please Contact Customer Support Team and include the UUID from the Headers or Response to facilitate problem tracking

Quick Start​

  1. Choose Wallet Mode - Select Seamless Wallet or Transfer Wallet based on business requirements
  2. Obtain API Key - Contact Customer Support Team to obtain a test environment key
  3. Read Documentation - Read the API Documentation for the corresponding wallet mode in detail
  4. Test Integration - Complete API integration in the test environment
  5. Go Live Deployment - Apply for the production environment and then deploy live

Additional Recommendations​

Screen Wake Lock Permission Description (Screen Wake Lock)​

  • Enable screen wake lock to prevent the device screen from automatically dimming or turning off. "Property Definition": When using <iframe> to embed a service page, you must explicitly declare a permission policy, otherwise the browser will block the function for security reasons.
<iframe 
  id="vp-service-monitor" 
  src="https://api.example.com/v1/monitor" 
  allow="screen-wake-lock"
  style="width: 100%; height: 600px; border: none;">
</iframe>