Member Interlink (GET Method)

What is a member interlink?

This feature applies your service’s member authentication to the Contiple Help Center, allowing users to submit member-only inquiries and view their submitted inquiry history.

---

➊ Member Interlink

1-1. Overview

• Member integration supports two types of API methods: GET and POST.

  • POST Method

    • This method is suitable for services provided on web-based platforms (PC or Mobile).

    • The service must provide a web-based login page (URL).

    • Two implementation types are supported, as defined in the development specifications: Client-side, Server-side

  • GET Method

    • This method is suitable for services that do not provide a web-based login page.

    • Recommended for native application–based services (non-web).

• To enable integration, please implement the API according to the specifications provided by Contiple and register it in the Member Integration settings.

---

1-2. Process (GET Method)

1

Accessing the Help Center

• When a user accesses the Help Center from the app, the Help Center is opened using the specified URL format.

  • https://{org}.oc.nhncloud.com/{service}/hc/?usercode={User ID}&username={User Name}&email={User Email Address}&phone={User Phone Number}&token={Autentication Token Value}

2

Token Verification URL Call

• The Help Center calls the Token Verification URL to validate the token.

• The Token Verification URL must be implemented by the service provider according to the development specifications and registered in the Contiple member integration settings.

3

Accessing Inquiry Features

• If token verification is successful, the user can access Submit Inquiry or Inquiry History.

• If token verification fails, the user can submit inquiries only as a guest (non-member).

---

1-3. Member Authentication Method

1

Enable Member Integration

• Navigate to [Service Management] → [Help Center] → [Member Intelink].

• Enable the Member Integration Activation option to enable the feature.

2

Non Member Inquiry

• Enabled: Users can submit inquiries without logging in.

• Disabled: Only logged-in users are allowed to submit inquiries.

3

Login Type

• Select GET as the login method.

4

Token Verification URL

• This is the URL used to verify the token passed from your service when accessing the Help Center.

• Enter the Token Verification URL implemented according to the development specifications below, then click Save to complete the setup.

---

➋ Development Specifications

2-1. Token Generation

Contiple Organization Key

• You can find the organization key under: [Global Management] → [Contract Services Status] → [Organization Information]

Token Generation Rule

• Generate the token according to the sample below.

• The parameter order must strictly follow the sequence defined below.

  • In the example, the organization key is stored in Sample project > application.properties > oc.apikey=.

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("&");
    sb.append(usercode); // 2
    sb.append("&");
    if (StringUtils.isNotBlank(username)) {
        sb.append(username); // 3
        sb.append("&");
    }
    if (StringUtils.isNotBlank(email)) {
        sb.append(email); // 4
        sb.append("&");
    }
    if (StringUtils.isNotBlank(phone)) {
        sb.append(phone); // 5
        sb.append("&");
    }
    　if (StringUtils.isNotBlank(memberno)) {
        sb.append(memberno); // 6
        sb.append("&");
    　}
    if (StringUtils.isNotBlank(returnUrl)) {
        sb.append(returnUrl); // 7
        sb.append("&");
    }
    sb.append(time); // 8

    SecretKeySpec signingKey = new SecretKeySpec(apiKey.getBytes("UTF-8"), "HmacSHA256");
    Mac mac = Mac.getInstance(signingKey.getAlgorithm());
    mac.init(signingKey);
    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", "[email protected]", "123456789",
    null, 1660095873001L, "7cf2828608274a49a3f06152b2188927");
    System.out.println(s); // Output: Ah9M58CQ9RFTShjFuqziQr+0MjmJxN6+bzWxMD71moo=
}

---

2-2. GET Member Authentication Method

(1) Interface Description

URL

• https://{org}.oc.nhncloud.com/{service}/hc/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

• https://{org}.oc.nhncloud.com/{service}/hc/ticket/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

• https://{org}.oc.nhncloud.com/{service}/hc/ticket/list/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

URL(Development)

• https://{domain}.oc.alpha-nhncloud.com/{service}/hc/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

• https://{domain}.oc.alpha-nhncloud.com/{service}/hc/ticket/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

• https://{domain}.oc.alpha-nhncloud.com/{service}/hc/ticket/list/?usercode=aaaabbb&username=yzg&[email protected]&phone=12345678901&time=12345678&token=8NPaBegAfbSvh1Lna9M0I1wBqjnoRyKO2r2izhuEAng%3d

Interface Name	Protocol	Request Format	Encoding	Response Format	Interface Description
GET 회원인증	HTTPS	GET	UTF-8		When accessing the Help Center, the service must pass customer information and an encrypted token as URL parameters.

---

(2) Request Parameter

Notes for token generation

1. If the token contains Korean characters, they should be used as-is without encoding.

2. When passing the token as a URL parameter, it must be encoded using the encodeURIComponent() method.

Name	Field (Parameter)	Type	Required	Description
Service ID	service	VARCHAR(50)	O	Service ID
User ID	usercode	VARCHAR(50)	O	User ID(Unique Value)
User Name	username	VARCHAR(50)	X	User Name
User Email Address	email	VARCHAR(100)	O	User Email Address
User Phone Number	phone	VARCHAR(20)	X	User Phone Number
Member No.	memberno	VARCHAR(50)	X	Member No.
Timestamp	time	LONG	O	Time unit: milliseconds
Authentication Token	token	VARCHAR	O	Generate the token using the following parameters and the organization key. Optional parameters that are null or empty must be excluded. The parameter order must strictly follow the specified sequence. SHA256Digest(service + usercode + username + email + phone + memberno + returnUrl + time)

---

(3) Response Data

• If token verification succeeds, the user is redirected to the member page.

• If token verification fails, the user is redirected to the non-member page.

• If access to inquiry history fails due to token validation, the user is redirected to the inquiry submission page.

---

2-3. Token Verification URL (By the Service)

(1) Interface Description

• URL: The URL must be provided by the service.

• URL(Development): The URL must be provided by the service.

Interface Name	Protocol	Request Format	Encoding	Response Format	Interface Description
Token VerificationURL	HTTPS	GET	UTF-8	JSON	The service verifies the token and userCode, then returns the result in JSON format.

---

(2) Request Parameter

Name	Field (Parameter)	Type	Required	Description
User ID	usercode	VARCHAR(50)	O	User ID(Unique Value)
Token generated by the service	token	VARCHAR	O	When accessing Contiple (Online Contact) via GET, the token must be included in the request.

---

(3) Response Body

로그인:
{
"login": "true",
"usercode":"usercodeXXX"
}


로그아웃:
{
"login": "false",
"usercode": null
}