​

KakaoTalk production patterns: Alimtalk and Friendtalk

​

1. Beta caveat: bring your own Biz Message credentials

1. Contract with a Kakao Biz Message reseller (NHN Cloud–contract gateway) and register your sender profile (발신프로필). You receive a gateway app key, a secret key, and a sender key.
2. Paste all three values in Orbit under Settings → Channels → KakaoTalk. Per-organization credentials take precedence over any platform default and are stored encrypted at rest.
3. Role caveat: until your credentials are connected, every send fails closed with CHANNEL_NOT_CONFIGURED (503).

​

2. Template registration walkthrough

1. Draft the template body with #{variable} placeholders for each recipient-specific value (name, order id, ETA).
2. Submit it through your reseller’s console and wait for Kakao approval. Re-submit after edits — an edited template is a new approval.
3. Reference the approved code as template_name (campaign message_template) and fill the placeholders with template_params (campaign variables).

curl -X POST "https://api.orbit.devotel.io/api/v1/campaigns/" \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Order confirmation — Alimtalk",
    "channel": "kakao",
    "type": "blast",
    "audience_type": "all",
    "message_template": "order_confirmation_kr_v1",
    "variables": { "order_id": "KR-90210", "eta": "2026-06-12" }
  }'

​

3. Choose Alimtalk vs Friendtalk

​

4. Fallback when the recipient is not a friend

1. On a failed delivery-status event where metadata.kakao_message_type is friendtalk, re-route the recipient to an approved Alimtalk template with equivalent content (“join the channel as a friend for promos” keeps a working template on file for this escalation).
2. Record the recipient’s preference on your own contact model so later promotional pushes skip Friendtalk for that recipient until a follow event proves the relationship.

​

5. Bulk vs one-off sends

• One-off / transactional: POST /messages/kakao (capped at 80 requests/minute per organization) or a small batch job. Use it for OTPs and per-recipient confirmations.
• Bulk: the Campaigns API. A campaign throttles, retries, and reports per recipient; a loop over the direct endpoint burns the per-organization minute cap and returns 429 RATE_LIMITED.

​

6. Tracking: kakao_message_type and suppression handling

​

7. Payloads that pass vs fail VALIDATION_ERROR

{
  "to": "821012345678",
  "body": "Your order has shipped — track it in the Orbit app.",
  "metadata": { "kakao_message_type": "friendtalk" }
}

{
  "channel": "kakao",
  "message_template": "order_confirmation_kr_v1",
  "variables": { "order_id": "KR-90210", "eta": "2026-06-12" }
}

{
  "to": "821012345678",
  "metadata": { "kakao_message_type": "friendtalk" }
}

{
  "to": "821012345678",
  "body": "Your order has shipped."
}

​

8. Handover: one template, a pick-list of channels

​

See also

• KakaoTalk channel page — field reference, error codes, and credential handling.
• APAC channels onboarding — LINE, WeChat, Zalo, and the fold-in of KakaoTalk.
• Template-only Asia channels playbook — one approved template across every template channel.
• Campaigns API — bulk sends.
• Message suppression — per-recipient opt-out handling.