This document introduces the webhook test feature provided by Kakao Developers.

You can use the webhook test tool to verify whether your implemented webhook works correctly or to check the format of incoming requests. For more details about webhooks, refer to Webhook.

There are two ways to use the webhook test feature:

• Actual webhook delivery: If you have registered a webhook URL, the webhook request will be sent to the registered webhook URL.
• Request preview: If you have not registered a webhook URL, you can preview a sample webhook request.

You can test all types of webhooks provided by Kakao Developers in [Tools] > [Webhook Test]. The test feature only triggers change events and does not actually modify the user's status or information.

You can test the webhook sent to your service when a user unlinks from your app. For the webhook request specification, refer to Unlink webhook.

Unlink webhook test

1. [A] App: Select the app you want to test.
2. [B] Webhook URL: Check the webhook URL to receive the webhook. If no webhook URL is specified, click [Set] and set the unlink webhook.
3. [C] Kakao Account: Select the team member's Kakao Account to test. The selected account must be linked to the app.
4. [D] Parameter: Set the event properties. (Note: Webhook request body.)
5. [E] Send: Click to send the webhook. If the webhook URL is not registered, click [Request Preview] to check the sample request. (Note: Webhook request example.)

You can test account status change events such as link, unlink, and consent or withdrawal of consent for Kakao Account. For the webhook request specification, refer to Account status change webhook.

Account status change webhook test

1. [A] App: Select the app you want to test.
2. [B] Webhook URL: Check the webhook URL to receive the webhook. If no webhook URL is specified, click [Set] and set the account status change webhook.
3. [C] Category: Select a category.
   • The test tool also allows you to test RISC and CAEP categories, which require special permissions.
4. [D] Event Type: Select the event type to send for testing. (Note: Supported event types)
5. [E] Kakao Account: Select the team member to send the event to. The selected account must be linked to the app.
6. [F] Parameter: Set the event properties. (Note: Webhook request body)
7. [G] Send: Click to send the webhook. If the webhook URL is not registered, click [Request Preview] to check the sample request. (Note: Webhook delivery result)

After selecting [Send], the test information appears at the bottom of the page, as shown below.

• Webhook request: Full text of the test request. Host and URL are excluded in the output when the webhook URL is not set.
• Security event Token: The decoded value of the SET contained in the request is displayed. The header and payload are output respectively. Refer to this when debugging.

The account status change webhook test page provides not only the Webhook request but also additional information such as the Security event token and Webhook response.

This is the decoded value of the SET information included in the webhook request. It is divided into Header and Payload.

// Header
{
  "kid": "ea5d255f34921d4a6ca10f6cadf270",
  "typ": "secevent+jwt",
  "alg": "RS256"
}

// Payload
{
  "aud": "8c67bxxxxxxxxxxxxxxxxxxxxxxe2e76140",
  "sub": "701541",
  "iss": "https://kauth.kakao.com",
  "txm": "1d61d6c8-173b-488c-b8af-2e2b6ca29777",
  "iat": 1744789997,
  "jti": "7185208e-c045-41e9-a2ff-0b219b9e123e",
  "events": {
    "https://schemas.openid.net/secevent/oauth/event-type/user-linked": {
      "subject": {
        "sub": "701541",
        "subject_type": "iss-sub",
        "iss": "https://kauth.kakao.com"
      }
    }
  }
}

This is an example of a webhook request sent by Kakao to your service. If the webhook URL is not registered, the Host header is not included.

POST / HTTP/1.1
Host: example.com
Content-Type: application/secevent+jwt
Accept: application/json

xxxXXXyYYYNmNhMTBmNmNhZGYyNzAiLCJ0eXAiOiJzZWNldmVudCtqd3QiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiI4Yz

You can check how your service endpoint responds to the webhook request. If the webhook URL is not registered, this is not provided.

HTTP/1.1 403 Forbidden

Alt-Svc: h3=":443"
ma=93600,h3-29=":443"
ma=93600,quic=":443"
ma=93600
v="43"
Cache-Control: max-age=0
Connection: close
Content-Length: 359
Content-Type: text/html
Date: Wed, 16 Apr 2025 07:54:35 GMT
Mime-Version: 1.0

Elapsed time: 582ms

You can test the webhook sent to your service when a Kakao Talk message shared with a user is successfully delivered. For the webhook request specification, refer to Kakao Talk share webhook.

Kakao Talk share webhook test

1. [A] App: Select the app you want to test.
2. [B] Webhook URL: Check the webhook URL to receive the webhook. If no webhook URL is specified, click [Set] and set the Kakao Talk Share webhook.
3. [C] Parameter: Set the event properties. (Note: Webhook request body)
4. [D] Send: Click to send the webhook. If the webhook URL is not registered, click [Request Preview] to check the sample request. (Note: Webhook request example)

You can test the webhook sent to your service when a user adds or removes a Kakao Talk channel linked to your app. For the webhook request specification, refer to Kakao Talk Channel webhook.

Kakao Talk channel webhook test

1. [A] App: Select the app you want to test.
2. [B] Webhook URL: Check the webhook URL to receive the webhook. If no webhook URL is specified, click [Set] and set the Kakao Talk Channel webhook.
3. [C] Kakao Account: Select the team member to send the event to. The selected account must be linked to the app.
4. [D] Parameter: Set the event properties. When testing, the Kakao Developers channel ID is used.
   (Note: Webhook request body)
5. [E] Send: Click to send the webhook. If the webhook URL is not registered, click [Request Preview] to check the sample request. (Note: Webhook request example)