Updates on Kakao Developers app and app keys

This document describes the major changes to Kakao Developers app and app keys that have been updated on December 3, 2025.

Action required

The changes are automatically migrated, so you can use existing features without any additional action. However, menu locations and usage methods have changed significantly, so check your settings by referring to this document.

If you are using the services below, you must check the relevant information.

Service in use	Reference
Kakao Login or Kakao Sync	2. Platform information configuration location changed
Kakao Talk Share or Kakao Talk Message	4. Configure different links by purpose, 5. Message template tool setting options added and UI changed
APIs called with Admin key	3. Configure allowed APIs that can be called with Admin key

Changes

Summary

You can now configure platform information and product-specific information registered in the Kakao Developers app by app key. The major changes are as follows.

1. You can create up to 5 app keys per platform environment in an app.
   • (Note: 1. Add app keys by environment)
2. The configuration location of some platform information (web domain, redirect URI, etc.) has changed to under app keys.
   • (Note: 2. Platform information configuration location changed)
3. You can allow or disallow the APIs that can be called with Admin key.
   • (Note: 3. Configure allowed APIs that can be called with Admin key)
4. Link configuration location has changed by purpose. API call validation is managed in [Platform Key], and Kakao Talk Message link configuration is managed in [Product Link].
   • (Note: 4. Configure different links by purpose)
5. App scheme selection options and link preview features have been added to the message template tool.
   • (Note: 5. Message template tool setting options added and UI changed)

1. Add app keys by environment

• Target: REST API key, JavaScript key, Native app key, Admin key

Target	Before update	After update
App creation limit	1 per app key	5 per app key
App key management	1 key issued per type when creating an app	Same as before (1 key issued per type when creating an app), but you can register up to 5 keys per app key. You can set a primary key per app key. You can delete app keys. You can name app keys.
Configuration location	All 4 types of app keys configured in [App] > [General] > [App keys].	Configuration location differs by key type. - REST API key, JavaScript key, Native app key: [App] > [Platform Key]. - Admin key: [App] > [Admin key].

For existing users

• App key types remain unchanged.
• App keys created before the update have been migrated and set as primary keys.
• Even after the update, 4 types of app keys are automatically created (1 each) when creating an app, same as before. The first created key is set as the primary key.

2. Platform information configuration location changed

• Target: Web domain, native app platform information, redirect URI, client secret, allowed IP configuration

Before update

After update

Platform information registered in the app applied to all app keys.

You can configure platform settings per app key. - REST API key: Redirect URI (Login/Business Authentication), client secret (Login/Business Authentication), allowed IP configuration. - JavaScript key: JavaScript SDK domain (previously 'Site domain'), Kakao Login redirect URI. - Native app key: Android package name, key hash, iOS bundle ID, store URL. - Admin key: Allowed IP configuration, available APIs.

Example

For existing users

You can use existing features without any additional configuration, but if you need to modify settings, you must modify the information under the key that matches your platform environment. For example, if you need to modify the redirect URI in a service using Kakao Login with JavaScript SDK, modify the redirect URI under JavaScript key.

Configuration in use	Before update	After update
Redirect URI (Kakao Login/Business authentication)	Configured under [Product settings].	Configured under REST API key, JavaScript key.
Client secret	Configured under [Product settings].	Configured under REST API key.
Allowed IP configuration	Configured in [App] > [Advanced].	Configured under REST API key, Admin key.
Site domain	Configured in [App] > [Platform] > [Web].	Name and configuration location changed to allow separate use by purpose. - API call authentication: [Platform Key] > [JavaScript key] > JavaScript SDK domain. - Product link configuration: [Product Link] > Web domain. (Note: 4. Configure different links by purpose)
Android platform information (Package name, key hash, store URL)	Configured in [App] > [Platform] > [Android].	Configured under Native app key > [Android app information].
iOS platform information (Bundle ID, store URL)	Configured in [App] > [Platform] > [iOS].	Configured under Native app key > [iOS app information].

3. Configure allowed APIs that can be called with Admin key

• Target: Admin key

Before update	After update
All APIs can be called with one Admin key.	You can directly configure APIs to allow or restrict per Admin key. (Note: Available APIs). You can create additional Admin keys (up to 5) and use them by purpose. You can manage them separately by usage to enhance security.

For existing users

• Admin keys created before the update have been migrated with all APIs allowed. If you need to restrict APIs, see Available APIs to restrict APIs.
• The detailed API list is displayed based on the permissions granted to the app in use. See Admin key: API category to select the category you want to use.

4. Configure different links by purpose

• Target: Web domain, Android platform information (Package name, Key hash, Store URL), iOS platform information (Bundle ID, Store URL)

Before update

After update

Platform information set in [App] > [General] > [Platform] was applied to both API validation and Kakao Talk Message template link settings.

The location to configure platform information differs depending on its purpose. - API call validation: Register the required information in [App] > [Platform Key]. - Kakao Developers product link settings: Set in [App] > Product Link. Note: - When using a Default template: Changing the Default native app scheme used in the template may change the app launch link. - When using a Custom template: Changing the native app scheme in Common settings of the message template tool may affect the app launch link.

API validation

Kakao authenticates clients using SDKs with the information below. When using Kakao SDK for Android, iOS, or JavaScript, you must register the platform information below in the Kakao Developers app to call APIs.

• Android: Package name, Key hash
• iOS: Bundle ID
• JavaScript: JavaScript SDK domain

For existing users

You can use existing features without any additional configuration, but if you need to modify settings, you must modify the information in the path below by purpose.

Configuration	Before update	After update
Site domain	Set in [Platform] > [Web] > [Site domain].	Configuration location depends on the purpose. - For API validation using the JavaScript SDK: Set JavaScript SDK domain under JavaScript key. - For product links: Set Web domain in Product Link.
Android platform information (Package name, Key hash, Store URL)	Set in [Platform] > [Android].	Set under Native app key.
iOS platform information (Bundle ID, Store URL)	Set in [Platform] > [iOS].	Set under Native app key.
Link settings for Kakao Talk Share or Kakao Talk Message	Only information registered in [Platform] > [Web], [Android], or [iOS] can be used.	Configure separately in Product Link. - Web domain: Register the domain to be used for product links. - Native app scheme: Check the custom URL scheme and select the default native app scheme.

5. Message template tool setting options added and UI changed

• Target: Message template tool
• Detailed changes:
  • New setting option
  • Component link configuration UI changed
  • Component link value display method

New setting option

• [Common settings] > [Native app scheme]: You can select a scheme to apply to the template from the native app schemes configured in app keys.

Distinction	Header	Description
🅐	[Default native app information]	Scheme specified as Default native app scheme in [App] > [Product Link] > [Native app scheme].
🅑	[Key name]	Custom URL scheme of the Native app key. The key name set by the user in [Platform Key] > [Native app key] is displayed as the header.

For templates created before December 3, 2025, they have been migrated with existing app key (primary key) information instead of the default native app scheme.

For existing users

• The [Native app scheme] of message templates created before the update has been migrated based on the existing app key set as the primary key.
  • A custom URL scheme, named [Default LEGACY_NATIVE_APP_KEY] or [Default Native AppKey], is selected.
  • The migrated scheme is also applied to [Default native app information] in the same way.
• To update the default app scheme, first create a Native app key under [Platform Key], then set this as the default native app scheme in [Product Link].
• When changing the default app scheme, note that behavior may vary depending on which native app information is selected in Common settings in the message template tool:
  • If [Default native app scheme] is selected: Make sure that the app execution link (Android/iOS store links, etc.) are also updated.
  • If [Default LEGACY_NATIVE_APP_KEY] or [Default Native AppKey] is selected: The settings remain as the previous key information.

Component link configuration UI changed

The UI for Component link settings in the message template tool is updated for you to use easier.

Before update	After update
Enter the domain configured in [App] > [Platform] > [Site domain] directly. When using User arguments, if the registered domain is not passed as a user argument, it is replaced with the first value of the registered domains.	You can select one from the domain list below: - 🅐 Default web domain. - 🅑 Web domain value: Domain configured in [Product Link] > [Web domain]. - 🅒 User arguments: If the registered domain is not passed as a user argument, it is replaced with the default web domain value. When selecting a domain, you can preview the link.

Component link value display method

The value display method in Component link settings has been improved for better clarity and readability.

Before update

After update

When using values registered in [Platform], internal reserved words are displayed. (Example: ${REGI_WEB_DOMAIN}, ${A_E}, ${A_M}, ${I_E}, ${I_M})

The configuration value where the link redirects is displayed instead of reserved words. Web domain - When default web domain is selected: Default web domain is displayed. - When one of the web domain list is selected: Original domain value is displayed (Example: https://developers.kakao.com). - User arguments: Entered user argument value is displayed (Example: ${web_domain}). Native app scheme - If default native app scheme is selected in Common settings: Default native app scheme is displayed. - If a specific key's native app scheme is selected in Common settings: The corresponding scheme value is displayed.

See more

• Platform key / Admin key
• Product Link
• Message template > Custom template