Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Kakao authentication

Kakao authentication lets your users sign in with a Kakao account (popular in Korea). Once connected, you can offer “Continue with Kakao” in your WeWeb app.

What this integration supports

  • Social sign in with Kakao
  • Redirect to different pages for success, error, and first-time users

Setup in Kakao Developers

You create an app in Kakao Developers, enable Kakao Login, and register WeWeb’s redirect URL (the URL Kakao sends users back to after sign in).

1. Create an app and enable Kakao Login

  1. Go to Kakao Developers.
  2. Create an app (or open an existing app).
  3. Open Kakao Login → Enable and set the state to ON.

2. Register the redirect URI

Kakao requires you to register a redirect URI for Kakao Login.

  1. In your app settings, open App → Platform.
  2. In the Redirect URI section, add:
    • https://<your-domain>/api/auth/callback/kakao

If you use multiple environments, add a redirect URI for each environment (preview, staging, production).

3. Get your keys

In your app settings, copy:

  • REST API Key (You will use this as REST API Key in WeWeb)
  • Client Secret (Enable it if it is off, then copy it)

Connect Kakao in WeWeb

  1. In the WeWeb editor, go to Data & API → Auth → Integrating providers.
  2. Find Kakao and expand it.
  3. Turn on the Enable toggle.
  4. Fill in:
    • REST API Key
    • Client Secret
  5. Click Save.

WeWeb stores these values as environment variables (for example PROVIDER_KAKAO_CLIENT_ID and PROVIDER_KAKAO_CLIENT_SECRET).

Test sign in

  1. In Interface, add a “Continue with Kakao” button.
  2. Create a workflow on click and add Sign in with social provider.
  3. Set:
    • Provider: kakao
    • Success page, Error page, And (optional) New user page
  4. Preview your project and complete the Kakao sign-in flow.

For what to do after sign in (roles, private pages, and access checks), see Users and roles overview →.

Common pitfalls

Redirect URI mismatch (KOE006)

If you see a KOE006 error during sign in, Kakao usually considers your redirect URI invalid.

  • In Kakao Developers, confirm you registered https:///api/auth/callback/kakao as a redirect URI.
  • Make sure the domain matches the environment you are testing (preview vs production).

Kakao Login is disabled (KOE004)

If you see a KOE004 error, Kakao Login is not enabled for your app.

  • In Kakao Developers, open Kakao Login → Enable and set it to ON.

Email not returned for some users

Kakao can require extra setup if you want to retrieve the user’s email.

  • In Kakao Developers, review the consent items you request in Kakao Login settings.
  • If you need email for all users, check Kakao requirements for business verification (Biz App).

Reference

WeWeb settings

Setting in WeWebDescriptionWhere to find it in Kakao Developers
REST API KeyPublic identifier for your Kakao app (used for login).App settings → App → PlatformREST API Key.
Client SecretSecret used to securely complete sign in.App settings → App → PlatformClient secret.

FAQs

Which redirect URI should I register in Kakao Developers?

Register https://<your-domain>/api/auth/callback/kakao. Add one redirect URI per environment you use.

What provider value should I use in the workflow action?

Use kakao as the Provider value in the Sign in with social provider action.

Continue learning

Now that Kakao sign in works, learn how to protect pages and data using roles.

Users and roles overview →