API Overview

This is the common guide you should read before you start integrating with the Bizgo API.
On this page you will find everything in one place: how to issue an API Key, the Base URL, authentication headers, the request/response body structure, and firewall and security settings.

QUICK NAVIGATION

API guide shortcuts

STEP 1

🧭

Common guide

Follow the first-time integration order

💬

Communication API

Send specifications for each channel

🔐

Verify API

2FA and social login specifications

API key

An API Key is the basic credential that identifies and authenticates whoever calls the Bizgo API.
Never expose it directly in the browser — keep it in a server environment variable or a secure secret store.

How to issue and check an API key

Sign in to Bizgo and complete business verification.
Select the workspace you want to use in the console.
From the workspace dashboard, go to 연동관리 (Integration management), copy the issued unified API Key, and use it for your server integration.

Authentication and other header settings

The Bizgo API uses HTTPS-based REST calls.
Only the path differs between products — the authentication method and the base header rules stay the same everywhere.

Base URL

Product (production)

Check IPs

https://mars.ibapi.kr

Sandbox (test)

Check IPs

https://sandbox-mars.ibapi.kr

How to use Sandbox

Sandbox uses the same API key as production, but it is a test environment where no real message is sent. Right after a key is issued or changed, it can take up to 10 minutes to take effect.

In both the production and test environments, calls are only accepted from public IPs that you allowed in advance. You can find the full list of allowed IPs in Firewall and security protocols.

Request headers

Content-Type: application/json
Authorization: API KEY

Request and response body

The request body uses JSON format.
The response body is split into a common part (common) and an individual part (data). The common part carries the authentication and permission check result, and the individual part carries the processing result of the actual product API.

Encoding

The default encoding for the Bizgo API is UTF-8 .

For text messages (SMS/LMS/MMS), however, Korean carrier specifications mean you can send content that includes EUC-KR characters.

Build the request body structure to match the API specification of each product.
Message APIs use common fields such as destinations, messageFlow, and ref, while the channel-specific detail fields are defined in each product specification.
In the response, common means the API Gateway common result and data means the actual product processing result.

{
  "destinations": [{ "to": "01000000000" }],
  "messageFlow": [
    {
      "sms": {
        "from": "01000000000",
        "text": "테스트 메시지"
      }
    }
  ],
  "ref": "req-20260331-001"
}

{
  "common": {
    "authCode": "A000",
    "authResult": "Success",
    "infobankTrId": "Infobank-Tracking-Id"
  },
  "data": {
    "code": "A000",
    "result": "SUCCESS",
    "data": {
      "destinations": [
        {
          "to": "01000000000",
          "msgKey": "SMS20260331-000001",
          "code": "A000",
          "result": "Success"
        }
      ]
    },
    "ref": "req-20260331-001"
  }
}

Firewall and security protocols

TLS

All API communication is provided over HTTPS (TLS).
TLS 1.2 or higher is supported.

Firewall allowed IPs

Production environment

Outbound direction (customer server → Bizgo API)
PORT 443
3.35.80.15, 43.203.83.174, 54.116.59.12
Inbound direction (Bizgo Webhook → customer server)
3.37.214.83, 3.39.75.204, 43.200.251.230, 211.115.98.154, 211.115.98.155, 211.115.98.205

Sandbox environment

Outbound direction (customer server → Bizgo API)
PORT 443
211.115.98.231
Inbound direction (Bizgo Webhook → customer server)
211.115.98.231

ACL (IP access control)

The public IP used to call the API must be registered in advance against the API Key.
If your development and production servers are separate, register the public IP of every environment.
Calls from an unregistered IP are blocked at the authentication or access control stage.

How to register an IP

Sign in to Bizgo, then go to 발송관리 > 연동관리 (Send management > Integration management) in the left menu of the console.
Register the public IPs you want to allow for the unified API Key you are using.
Add both your development and production server IPs, then save.

ACL IP registration screen example 1

Rate Limit

Call limits may apply per API.
The current default Rate Limit is 200 TPS for send APIs and 5 TPS for non-send APIs such as management, lookup, and report.
If you exceed the limit, you may receive 429 Too Many Requests or an equivalent policy error.
For bulk sends or repeated lookups, we recommend retrying with exponential backoff.

About the Rate Limit baseline

The values above are the current defaults and may change later depending on service operation policy, account status, and API type.

Recommended security checklist

Keep the API Key only in a server environment variable or a secret store.
Mask sensitive information such as API Keys, phone numbers, and payloads before writing them to logs.
We recommend keeping your outbound firewall policy open only to the Bizgo API domain and the allowed ports.