Integration management

To use the system integration sending service, you need to issue a unified key (통합 Key).

The unified key is a single authentication credential that lets you use every message product and service Bizgo offers through one integration.

Unified key issuance limit

You can issue up to 5 unified keys per team space. If you need more than 5, contact the support center.


Issue a unified key

To issue a unified key, select the team space you will use at the top of the console, then go to Bizgo (비즈고) > Developer tools (개발 도구) > Key management (KEY 관리). Click the Issue key (Key 발급) button on the page and enter a key management name (up to 20 characters).

Issue a unified key 1

Automatic issuance on first sign-up

When you sign up for the first time, one unified key is issued automatically once business verification is complete, and you will see it with products already added according to the plan you selected.

Issue a unified key 2

After issuing the unified key, set the allowed IPs (ACL) and connect the products you want to use to activate the key. If the key list shows Setup required (설정 필요) right after issuance, the key cannot send yet. Add the allowed IPs with Register IP (IP 등록하기) and connect the message products with Add product (상품 추가).

Setting a key management name makes it easier to keep track of things when you manage several keys.

Rules for allowed IPs

Only the IPv4 format is accepted, and up to 10 addresses are registered per key. You can also give a range — use the 192.168.0.0/24 or 192.168.0.* form.

The send type cannot be changed later

Under Add product (상품 추가) you choose between OMNI API (REST) and OMNI AGENT (installed). Once set, it cannot be changed. Confirm the choice with your developer before you select it.

Check that the issued key shows the In use (이용중) status in the list. To see the full key value, click Show all keys (Key 전체 보기) and enter your password once more; Details (상세) shows the connected products and the secret key.

Check the unified key


Check product API/AGENT details

Once you have issued the unified key and connected the products you want to use, you can review the specification and details of the API or AGENT.

For communication products you can review the specification, development documents and installation files, the services in use, the report receiving method, and the monthly/daily send limits — and you can change the report receiving method.

What is report receiving?

This option controls whether your system receives reports on the final delivery result of messages sent with communication products, and how those reports are delivered.

Issue a unified key 3

MethodDescription
Not used (사용 안 함)Your system does not receive the final delivery result.
POLLINGReports are returned each time your system requests them.
WEBHOOKEach time a final delivery result is created, the report is sent to your WEBHOOK URL.

How long a report receiving change takes to apply

You can edit the report receiving method. After a change, it takes up to about 15 minutes for the updated setting to take effect.


Base URI

EnvironmentBase URI
Productionhttps://mars.ibapi.kr/api/comm
Sandboxhttps://sandbox-mars.ibapi.kr/api/comm

Authentication header

Include the headers below in every API request.

TEXT
Authorization: ApiKey {발급받은 API 키}
Content-Type: application/json

Request example

1curl -X POST https://mars.ibapi.kr/api/comm/v1/send \
2 -H "Authorization: ApiKey YOUR_API_KEY" \
3 -H "Content-Type: application/json" \
4 -d '{ ... }'

Notification center

You can be alerted the moment something goes wrong with a Bizgo service. You subscribe to alerts per unified key issued in Integration management, and you can freely choose the receiving channels and the alert items.

Configure this from Bizgo (비즈고) > Developer tools (개발 도구) > Key management (KEY 관리) by clicking Get system alerts (시스템 알림 받기).

Notification center

Alert items

You can select more than one alert item.

Alert items

ItemDescription
Service noticesNotices for scheduled work and incidents
Account alertsAccount-related alerts such as insufficient credit or Rate Limit exceeded
What's newAnnouncements about new feature updates

Receiving channels

You can receive alerts on any of the channels below, and you can register several channels at once.

Receiving channels

ChannelDescription
SlackReceive in a Slack channel through a Webhook URL
Microsoft TeamsReceive in a Teams channel through an Incoming Webhook
Google ChatReceive in a Google Chat space through a Webhook URL
DiscordReceive in a Discord channel through a Webhook URL
WebhookReceive an HTTP POST request at a URL you configure yourself

How alerts are registered

Alerts are registered per unified key issued in Integration management. You can configure the receiving channels and alert items independently for each key.


Next steps