본문 바로가기
Documentation menu

BUILD IN YOUR LANGUAGE

샌드고 SDK 및 개발자 가이드

Connect SMS, Alimtalk and Brand Messages with 19 official SDKs. Find installation steps and sending examples for your language and framework.

Your language. Your workflow.

One install command to get started.

Find official packages and examples for your language, framework or automation tool.

19official SDK packages

Results 20

Server core SDKs

7

Framework integrations

9
Complete guide to choosing and using SDKs

Sendgo publishes 19 official language and framework SDK packages for Kakao Alimtalk, Brand Message and SMS/LMS/MMS. The OpenAPI specification is provided separately and is not counted as an SDK. Whichever language you use, the integration follows the same shape: issue keys → register a sender → send.

Get started in three minutes

  1. Issue keys — sign in and open API/SDK → API integration to create an access key and a secret key.
  2. Register a sender — register a Kakao sender profile under Kakao channel for Alimtalk and Brand Message; register a caller ID under Sender numbers for SMS.
  3. Install the SDK — open the guide for your language and run the one-line install command.
  4. Send — pass a template code and a recipient list. That is the whole flow.

How the SDKs are structured

Every SDK follows a core + framework extension pattern.

Core Framework extensions
sendgo/php sendgo/laravel, sendgo/symfony, sendgo/wordpress
@sendgo/node @sendgo/react, @sendgo/vue, @sendgo/nestjs
sendgo-python sendgo-django, sendgo-fastapi
io.sendgo:sendgo-java io.sendgo:sendgo-spring
sendgo (Ruby) sendgo-rails
Sendgo.SDK Sendgo.AspNetCore

The core is a plain client with no framework dependency. Each extension wraps that core to fit the framework's configuration, dependency injection and logging conventions. Installing an extension pulls in the core as a dependency, so you never install both.

Concepts shared across every SDK

  • Authentication — exchange your access key and secret key for a token, then authenticate with a Bearer token. Every SDK issues and refreshes the token for you.
  • API version — use v2. It uses signature-based tokens (sgv2.{payload}.{signature}) valid for 24 hours.
  • Channels — Alimtalk (alimtalk), Brand Message (brandMessage), SMS/LMS/MMS (sms), Friendtalk (friendtalk, discontinued 2025-12-31 — requests are delivered as Brand Message free-form automatically).
  • Brand Message — the successor channel to Friendtalk. It reaches recipients who are not channel friends and can broadcast to every consenting channel friend.
  • Short URL — shortens links in your messages and counts the reaction (daily series, device, referrer, country). v2 only.
  • SMS fallback — replaceSms falls back to SMS automatically when a Kakao message fails.
  • Scheduling — scheduleType: SCHEDULED with an at timestamp.
  • Errors — every SDK raises an exception carrying the HTTP status and the Sendgo error code. See the REST API reference for the full code list.

Server-only SDKs

@sendgo/react, @sendgo/vue and sendgo_flutter are server-side only. Your access key and secret key must never ship in a browser bundle or a mobile app, so use them exclusively from a server context — a Next.js Server Action or Route Handler, a Nuxt server route, a Dart backend.

Resources for AI coding agents

If you are integrating with an AI assistant or a coding agent, these endpoints give it accurate source material.

  • /llms.txt — a map of the whole documentation set (llmstxt.org convention)
  • /llms-full.txt — every SDK guide concatenated into one file
  • /{lang}/sdk/{package}.md — the raw markdown of any guide
  • /openapi.yaml — the OpenAPI 3.0.3 description of the REST API
Focus on building. Leave messaging to Sendgo.Back to top ↑