Authentication overview

The Bizgo Verify API offers two authentication methods for service sign-up, login, and identity verification.
You can use two-factor authentication and social login on their own or combine them, depending on your goal.

Authentication services

Two-factor authentication

Send and verify verification codes over SMS, Kakao, or RCS to implement two-step authentication.

Go to two-factor authentication →

Social login

Implement fast sign-up and login with Kakao, Naver, Google, and Apple social accounts.

Go to social login →

Complete the steps below before you use two-factor authentication or social login.

Sign up from the Bizgo website with Quick sign-up.
After signing up, complete business verification (enter your business registration number and upload your business registration certificate; 1–2 business days).
Create a team space.

Operational prerequisites

Check everything you need before actual use in one place — sign-up, business verification, team spaces, and member invitations.

View operational prerequisites →

Two-factor authentication

To use the two-factor authentication API, first issue a unified KEY and connect the products you want to use.
A unified KEY is the credential that lets you use Bizgo messaging products and authentication services through a single key.

Step 2 · Issue a unified KEY

Go to Team space in the console.
Select Integration management in the left menu.
Click the Issue KEY button to issue a unified KEY.
Connect the two-factor authentication product to the unified KEY and register the IP ACL for your calling server.

Issued automatically on first sign-up
When you sign up for the first time, one unified KEY is issued automatically after business verification is complete. Depending on the plan you chose, you will see it with the two-factor authentication product already connected.

Integration management

Check how to issue a unified KEY, set up IP ACL, connect products, and build the authentication header.

View unified KEY issuance →

Step 3 · Register your service name

Call the service name registration API once
To show your service name in two-factor authentication messages, you must call the service name registration API once before you go live. The registered service name is then available in later verification code send requests.
API: POST /api/verify/v1/2fa/service/regist
Full spec: API reference — Verify 2FA service name registration

Example message with a registered service name

TEXT

Your verification code is [123456].
This message was sent from [Bizgo] via Infobank.

Example message without a registered service name

TEXT

Your verification code is [123456].
This message was sent via Infobank.

Social login guide

See in detail how to integrate Kakao Sync and Naver login, and how to register your app information.

View the social login guide →

This product unifies the Kakao, Naver, Google, and Apple social platforms behind a single API to offer fast sign-up and login.
You can switch between social platforms with the single provider parameter.

Step 2 · Issue a unified KEY

Go to Team space in the console.
Select Integration management in the left menu.
Click the Issue KEY button to issue a unified KEY.
Connect the social login product to the unified KEY and register the IP ACL for your calling server.

Issued automatically on first sign-up
When you sign up for the first time, one unified KEY is issued automatically after business verification is complete. Depending on the plan you chose, you will see it with the social login product already connected.

Integration management

Check how to issue a unified KEY, set up IP ACL, connect products, and build the authentication header.

View unified KEY issuance →

Step 3 · Pre-configure Kakao and Naver Developers

Following the pre-configuration steps, create and set up an app in each provider's developer console.

Register the Redirect URI when you create the app in the provider's developer console
For Kakao and Naver, you must register the Bizgo callback URL exactly in the provider console so users return correctly after authentication completes.
Kakao : https://mars-verify-cb.ibapi.kr/api/callback/kakao
Naver : https://mars-verify-cb.ibapi.kr/api/callback/naver

Configure Kakao Sync

In Kakao Developers, work through the items required for Kakao Sync simple sign-up in order.

Setting	What to check	Path and notes
Basic information	Set the service information shown on the Kakao Sync simple sign-up consent screen. The app name, icon, and company name must match your actual service.	My Application > General Application
Test environment	You can use a test app and a developer channel so your live service is unaffected. Even a service that does not use Kakao Login yet can create a test app to develop the integration if needed.	My Application > Kakao Login Test app, developer channel
Kakao Login	You must enable Kakao Login to use Kakao Sync simple sign-up. Web services must register a Redirect URI.	My Application > Kakao Login Enable Kakao Login, register a Redirect URI
Simple sign-up	Set whether to use Kakao Sync simple sign-up, along with your service terms. When simple sign-up is enabled, your service terms appear as consent items on the consent screen.	My Application > Kakao Login > Simple sign-up Simple sign-up, enable simple sign-up
Consent items	Set the user information and feature permissions you receive from Kakao. Some consent items may require a separate review.	My Application > Kakao Login Consent items
Primary channel	Set the primary channel shown on the Kakao Sync simple sign-up consent screen.	My Application > Kakao Login > Kakao Talk Channel Primary channel setting

Kakao Redirect URI
In your Kakao Login settings, register https://mars-verify-cb.ibapi.kr/api/callback/kakao as a Redirect URI.

In Naver Developers, work through the items required for Naver login in order.

Setting	What to check	Path and notes
Register an application	Agree to the terms, register your account information, and register the application. When registering the application, set the API in use to Naver Login.	Application registration
Check the client ID and client secret	After the application is registered, check the client ID and client secret. Use those values in your Bizgo API requests or operational settings.	Client ID / secret

Naver callback URL
In your Naver login settings, register https://mars-verify-cb.ibapi.kr/api/callback/naver as the callback URL.

Step 4 · Call the app information registration API once

After pre-configuration, register the appId, client ID, and client secret issued by the provider, along with the callback URL.

Important App information registration
You must register your app information once before you can use social login.
Be sure to register the appId, client ID, client secret, and callback URL obtained during pre-configuration.
API: POST /api/verify/v1/social/app-config/regist
Full spec: API reference — Social login app information registration

Set up your environment — API key issuance, IP ACL, authentication header
Operational prerequisites — sign-up, business verification, sender information registration
Security policy — API key security and HTTPS policy