기업회원 신청 서류 안내
신청자 구분에 따라 재직증명서 또는 위임장을 함께 제출해 주세요.
신청자 구분에 따라 재직증명서 또는 위임장을 함께 제출해 주세요.
A PRACTICAL GUIDE
Korean law requires the caller ID to be pre-registered. How to register an SMS sending number and connect a Kakao channel, and where registrations usually get rejected.
이 가이드는 아직 번역되지 않아 English 문서를 표시합니다.
To send text messages or Alimtalk in South Korea you must register the sending number in advance. This is not a Sendgo policy — it is a legal requirement (전기통신사업법 §84-2, prohibition on caller ID spoofing).
This step is the usual bottleneck. Document review takes time, and most teams start it only after the code is written. Start it first.
| Key | Identifies | Used by |
|---|---|---|
senderKey |
A registered SMS sending number | SMS · LMS · MMS, and Alimtalk SMS fallback |
kakaoSenderKey |
A connected KakaoTalk channel (sender profile) | Alimtalk, Brand Message |
Alimtalk alone needs only kakaoSenderKey, but the moment you enable SMS fallback you also need senderKey. In practice almost everyone enables fallback, so prepare both.
Where this usually fails
Alimtalk needs a KakaoTalk channel, separate from the SMS number.
kakaoSenderKeySENDGO_KAKAO_SENDER_KEY=your_kakao_sender_key
SENDGO_SMS_SENDER_KEY=your_sms_sender_key
Where this usually fails
@-prefixed identifier, not the display name.An unregistered number fails at send time, not at signup.
| Code | Cause |
|---|---|
INVALID_KAKAO_SENDER_KEY |
Sender profile key does not exist or is not owned by this account |
SENDER_NOT_REGISTERED family |
SMS sending number unregistered or still pending |
Check the console shows approved, not "under review". Pending numbers do not send.
Everything above can be done from code — including mobile numbers.
| Target | API |
|---|---|
| SMS sending number (landline, representative, corporate, delegated) | POST /api/v2/senders |
| SMS sending number (mobile) | POST /api/v2/senders — ID document instead of PASS |
| Kakao channel verification code | POST /api/v2/kakao-senders/token |
| Kakao sender profile registration | POST /api/v2/kakao-senders |
For mobile numbers the console uses PASS identity verification; over the API you attach an ID document and a Sendgo operator verifies it. Numbers filed that way are never auto-approved.
Channel registration still needs a person to read the verification SMS — but they read it on your screen. See doing everything over the API.
From issuing an access key to sending a Kakao Alimtalk, with working code in Node.js, Python, PHP, Laravel, Java and Go.
Pick the organisation, issue API keys, register sender numbers and templates from a coding agent. Everything except topping up credit works without the console.
Kakao Alimtalk, Kakao Brand Message and SMS/LMS/MMS differ in what content they allow, what they cost and what you must set up first. Which to pick, by situation.
Pick the right Sendgo package for PHP, Laravel, Symfony, WordPress, Node.js, Next.js, NestJS, Python, Django, FastAPI, Java, Spring Boot, Go, Ruby, Rails, .NET, ASP.NET Core or Flutter.
Exchange an accessKey and secretKey for a bearer token, and call the Sendgo API with it. Differences between v1 and v2, token caching, and the 401/403 codes.