The game server can validate the token key of the logged in user by using the token, playerID, and DID returned from the game client after successful login.

If the game does not allow duplicate logins, you must manage the token key that has been verified or implement functionality managing the session key of the game itself created with this token key.

  • Request URL
    Common URL
    Distributed Environment URL
    Sandbox URL
    HTTP Method Post
    Content-Type text/html
    Data Format JSON
  • Request Header
    Field Name Description Type Required
    Authorization Returned token key after sign-in String Y
    ISCRYPT Encrypted data, 0=Not encrypted Integer Y
  • Request Body
    Field Name Description Type Required
    appid AppID of a game which user signed in String Y
    did Returned DID after sign-in String Y
    player_id Returned PlayerID of authentication v4 after sign-in Integer Y
    hive_certification_key Hive certification key(Issued by AppCenter) See more String N
  • Response
    Field Name Description Type
    result_code Verification result. 0=success More… Integer
    result_msg Result message String
  • Request Sample
  • Response Sample
  • Error Code
    Value Description
    0 Success
    2300 Required repayment for a refunded item
    4000 Invalid parameter
    4001 request json error
    4002 Hive certification key error
    5000 DB error
    5001 Invalid token in distributed environment (AWS)
    6000 Invalid AppID
    6001 IdP token error
    7000 Invalid token
    7001 No token in header field
    9999 Unknown error