Contact Center > Online Contact > API Guide for Developers > Member Integration (GET)

Member Integration


Member Intergration function is designed to apply membership confirmation process of the client to the Online Contact help center. Through this function, members of the client service could submit member inquiries, and check the history of previous inquiries. Member Integration is provided in two types: GET method and POST method. For integrating, API needs to be developed according to the development specifications Online Contact provide.

POST Method

  • It is suitable if the service you are trying to integrate is provided based on WEB on both PC and MOBILE platforms.
  • The login page of the service must be provided in WEB URL format.
  • Client-side API, Servicer-side API are provided.

GET Method

  • Suitable for services without WEB-based login page.
  • Suitable for Native APP services which are not WEB-based.

Process(GET Method)

① The user accesses to the help center within the APP. ② The client APP calls the help center through the URL format below. - https://{org}{service}/hc/?usercode={user_id}&username={user_name}&email={user_email}&phone={user_phonenumber}&token={verification_token_value} ③ Help center calls 'Token Verification URL'. ('Token Verification URL' must be developed according to the specifications provided below, and should be registered in member integration menu.) ④ If the verification result is successful after token verification, user gains access to 'Inquiry' or 'Inquiry History' page. If the verification fails, the inquiry will be submitted as non-member inquiry.

How to Integrate

① Access Service Management > Help Center > Member Integration ② Enable 'Member Integration' ③ Select whether to enable 'Non-member Inquiry'(If enabled, inquiries can be received even when the user is logged out, and if disabled, inquiries can be received only when the user is logged in) ④ Select the 'Login Type' which matches the characteristics of the service ⑤ Develop and register necessary API

Development Specifications

Create Authentication Token

The following is the authentication token generation sample. The order of parameters must be consistent with the given example. OC Organization Key is available at Global Management → Contract Service Status → Organization Information menu. (※ Save organization key in Sample project > > oc.apikey property)

private String getSHA256Token(String serviceId, String usercode, String username, String email, String phone,
        String returnUrl, Long time, String apiKey) throws Exception {
    StringBuilder sb = new StringBuilder();
    // Order by follow number:
    sb.append(serviceId); // 1
    sb.append(usercode); // 2
    if (StringUtils.isNotBlank(username)) {
        sb.append(username); // 3
    if (StringUtils.isNotBlank(email)) {
        sb.append(email); // 4
    if (StringUtils.isNotBlank(phone)) {
        sb.append(phone); // 5
     if (StringUtils.isNotBlank(memberno)) {
        sb.append(memberno); // 6
    if (StringUtils.isNotBlank(returnUrl)) {
        sb.append(returnUrl); // 7
    sb.append(time); // 8

    SecretKeySpec signingKey = new SecretKeySpec(apiKey.getBytes("UTF-8"), "HmacSHA256");
    Mac mac = Mac.getInstance(signingKey.getAlgorithm());
    byte[] rawHmac = mac.doFinal(sb.toString().getBytes("UTF-8"));
    return new String(Base64.encodeBase64(rawHmac));

// Sample
// Use this same input, the output is : Ah9M58CQ9RFTShjFuqziQr+0MjmJxN6+bzWxMD71moo=
public static void main(String[] args) throws Exception {
    String s = getSHA256Token("hangame", "testusercode", "testUsername", "", "123456789",
    null, 1660095873001L, "7cf2828608274a49a3f06152b2188927");
    System.out.println(s); // Output: Ah9M58CQ9RFTShjFuqziQr+0MjmJxN6+bzWxMD71moo=

Method of GET Member Verification

Interface Description


  • https://{org}{service}/hc/?usercode=aaaabbb&username=yzg&
  • https://{org}{service}/hc/ticket/?usercode=aaaabbb&username=yzg&
  • https://{org}{service}/hc/ticket/list/?usercode=aaaabbb&username=yzg&


  • https://{domain}{service}/hc/?usercode=aaaabbb&username=yzg&
  • https://{domain}{service}/hc/ticket/?usercode=aaaabbb&username=yzg&
  • https://{domain}{service}/hc/ticket/list/?usercode=aaaabbb&username=yzg&
Interface name Protocol Call direction Encoding Result format Interface description
GET Member Verification HTTPS GET UTF-8 When the help center is accessed from the service side, the interface is called by adding customer information and token value to the URL as parameters.


Name Variable Data type Required Description
Service ID service VARCHAR(50) O Service ID
User ID usercode VARCHAR(50) O User ID, indicates that the user is unique
Username username VARCHAR(50) X Username
User Email Address email VARCHAR(100) O User email
Phone Number phone VARCHAR(20) X Phone number
Membership Number memberno VARCHAR(50) X Membership number
Timestamp of Current Time time Long O Time unit: milliseconds
Authentication Token token VARCHAR O Calculated by the following parameters and organization key (SHA256). (If non-required parameter values are null or empty, exclude from creating token. Caution: The order of each value in the string must be consistent with the following example.) SHA256Digest(service + usercode + username + email + phone + memberno + returnUrl + time)
Precautions for Creating Authentication Token
  1. If korean alphabet is within the parameters, create the token directly in korean alphabet without encoding.
  2. Encoding by encodeURIComponent() is required when the generated token is used as URL parameter.

Result Data

  • Verification Success: Move to member access address
  • Verification Fail: Move to non-member access address
  • When user accesses 'Inquiry History' page from token verification failure state, the user is moved to 'Inquiry' page.

Token Verification URL(Service Side)

Interface Description

  • URL: Supported by service side
  • URL(Dev): Supported by service side
Interface name Protocol Call direction Encoding Result format Interface description
Token Verfication URL HTTPS GET UTF-8 JSON Service side checks the login status with token and usercode, and sends JSON format result value

Request Parameters

Name Variable Data type Required Description
User ID usercode VARCHAR(50) O User ID(Unique value)
Token Created by Service Side token VARCHAR O Token passed to Online Contact when the user logs in via GET method

Response Body

Logged in:
"login": "true",

Logged out:
"login": "false",
"usercode": null