페이지 이동경로
  • Docs>
  • Kakao Talk Share>
  • Troubleshooting

Kakao Talk Share

Error code

This document introduces the errors that may occur when using Kakao Talk Share and the solutions.

Error code

The list shows errors that may occur when using Kakao Talk Share API.

Error Code Status Code Cause Solution
4002 400 You sent a wrong request. Check the development guide and call the API according to the correct specification.
Refer to 4002 error occurs..
4003 400 You used the wrong app key or a temporary error occurred. Check if the app key used for the API call is correct, or try again later.
4005 400 You used an unsupported browser. Try again with a different browser or Internet Explorer version 11 or higher.
4006 400 You exceeded the default quota for Kakao Talk Share. Request a quota increase. Try again after the review is approved.
4007 400 You temporarily exceeded the usage limit. Try again later.
4008 400 A user whose Kakao Talk account is suspended cannot use Kakao Talk Share. Contact Kakao Customer Service.
4009 400 A non-admin user shared in an open chat room where [Admin only] option is enabled. Disable the [Admin only] option and try again.
4011 401 Authentication failed due to a wrong request. Check the app key used in the request.
Contact DevTalk.
4012 401 Kakao Account is not connected to Kakao Talk. Log in to Kakao Account in Kakao Talk's [More] > [Settings] > [Kakao Account] and try again.
4013 401 Kakao Account is suspended. Contact Kakao Customer Service.
4015 401 User registration failed. Try again later.
4016 401 Unauthorized request. -
4017 401 Kakao Account authentication failed. Try again later.
4018 401 A user logged in with a different Kakao Account before completing the share. Check the currently logged-in Kakao Account and try again.
4019 401 Authentication failed due to a wrong request. Refer to 4019 error occurs..
4020 401 Your Kakao Developers app or developer account has been suspended. Contact DevTalk.
4041 404 The URL shared to Kakao Talk is invalid. Pass the correct URL when calling the Kakao Talk Share API.
5001 500 Internal server error occurred. Try again later or refer to 5001 error occurs..
5005 500 Internal server error occurred. Try again later.

Case-by-case troubleshooting

The causes of problems vary depending on the situation. If the problem is not resolved with the methods below, contact DevTalk.

4002 Error

Cause
  • The domain of the shared URL is not registered in the app's Web platform
  • The specification of the requested message template does not match
  • The message template ID used for Kakao Talk Share is invalid
  • The SDK version is too low to support Kakao Talk Share functionality
Solution
  1. Check if the domain of the shared URL is registered in the Web platform of the Kakao Developers app. (Refer to Platform)
  2. When using message templates, call the API according to the correct specification. (Refer to: Development guide)
  3. Check if the message template ID registered in the app is correct, then request again. (Refer to: Custom template)
  4. Update to the latest version of the SDK.

4019 Error

invalid android_key_hash or ios_bundle_id or web_site_url

{"error":"misconfigured","error_description":"invalid android_key_hash or ios_bundle_id or web_site_url","error_code":"KOE009"}
Cause
  • The key hash passed from the app is different from the registered key hash
  • The bundle ID registered in the app is different from the actual service
  • The domain registered in the app is different from the domain passed in the request
Solution
  1. Check if the Web, Android, iOS platform information matches the actual service. (Refer to: Platform)
  2. Check if the domain passed in the request (caller value) is included in the domain list registered in [App] > [General] > [Platform] > [Web].
  3. For Android, check if the key hash used in the app matches the key hash registered in Kakao Developers, and add registration if necessary by referring to How to register key hash.
  4. When using Google Apps Script web app, refer to When using Google Apps Script web app to register the domain.
  5. When using an app distributed through App Distribution, refer to When using an app distributed through App Distribution to check and register the actual distributed app's key hash.
Reference documents

domain mismatched

[-401] domain mismatched! caller=https://xx. check out registered web domains.
Cause
  • The domain registered in the app does not match the domain passed in the actual API request
Solution
  1. Check if the domain passed in the request (caller value) is included in the domain list registered in [App] > [General] > [Platform] > [Web].
  2. When using Google Apps Script web app, refer to When using Google Apps Script web app to register the domain.

wrong appKey(null) format

{"name":"KAPIError","msg":"wrong appKey(null) format","code":-401}
Cause
  • You used an app key from a different app than the one where the domain is registered
  • You used an app key that does not match the platform you are using
  • The app key value is missing or has a typo
Solution
  1. Check if you are calling the API with the app key of the app where the domain is registered in Kakao Developers.
  2. Check if you are using the correct app key for the platform you want to use. (Refer to: Platform-specific app keys)
  3. Check if the entire app key value is passed without omission.

When using Google Apps Script web app

  1. Check if only the base domain is registered in the Web platform information, not the full URL.
    • (O) https://script.google.com
    • (X) https://script.google.com/macros/s/AKfycb.../exec
  2. When the web app runs inside an iframe, check if the actual domain where the iframe is loaded is registered as the site domain. For GAS web apps, URLs are provided in the pattern https://script.google.com/macros/..., but the actual content is loaded through an iframe, so the domain information may differ from the domain where the iframe is loaded.
  3. When using URL shortening services (e.g., bit.ly), register the final redirected domain as the site domain. Shortened URLs may not be recognized as valid site domains.

When using an app distributed through App Distribution

  1. To check which key hash is used in the distributed app, output and log the key hash inside the app.
    • Android: Log.d("KakaoSDK", message)
    • iOS: print("KakaoSDK: (message)")
    • JavaScript: console.log("KakaoSDK:", message)
    • Flutter: print(await KakaoSdk.origin)
  2. Compare the logged key hash with the key hash registered in Kakao Developers. If the two key hashes do not match, add the key hash confirmed in Kakao Developers to the app.
  3. If the problem persists, the app signing key certificate may have changed, so check the SHA-1 fingerprint of the app signing key certificate in Google Play Console again and regenerate the key hash. The regenerated key hash must be additionally registered in Kakao Developers.

5001 Error

Cause
  • Wrong parameter configuration
  • The image URL passed as a parameter is not accessible from outside (e.g., internal network, firewall) and the Kakao image scraping server failed to access
  • Cookie usage is restricted in the browser (Refer to: Error occurring in cookie-restricted environment)
  • Cookies do not work properly due to external factors such as Chrome extensions in the browser
Solution
  • Check if the image used for Kakao Talk Share is valid.
  • Check if the image used for Kakao Talk Share is accessible from outside.
    • When using a firewall on the service server, the image may not be displayed because the Kakao scraping server's access is blocked. Refer to Firewall to register the Kakao scraping server's IP in the ACL (Access Control List).
  • Check if cookie usage is not disabled in the browser.
  • Try the Kakao Talk Share functionality again in incognito/private mode. If it works normally, disable extensions that may affect cookies or browser behavior among the extensions installed in Chrome or other browsers, then try again.
Reference: Error occurring in cookie-restricted environment

Kakao Login and Kakao Talk Share functionality verify CSRF tokens to prevent Cross-Site Request Forgery(CSRF) attacks.

In environments where cookies do not work properly, even normal API requests may fail. Browsers with restricted cookie usage cannot send session IDs to the server, so the server cannot find the user's session and cannot verify valid CSRF tokens. As a result, the request is considered to have an invalid token and an error occurs.

DevTalk inquiry

If you cannot find a solution in this document, contact DevTalk with the following information.

  • [Required] App ID
  • [Required] UUID (Copy and paste the UUID value, not a screenshot of the error screen)
  • Detailed error message
  • SDK version if using SDK
Kakao Talk Share> Troubleshooting