26.09.11 September developer center documentation and feature update

Summary

The Kakao Brand Message catalog (FG) type is now reflected across the docs and Sandbox, and the CS Talk specification and common file upload parts have been filled in.

At a glance

• The Kakao Brand Message catalog (FG) type reflected in the specification, guide, Sandbox, and report
• Brand Message image upload specifications corrected against the Kakao source documentation
• Common file upload request parts (fileKey, imageName) applied to every channel
• CS Talk KakaoTalk identity verification, Rich message, and webhook receipt specifications expanded
• Notice for the new CS Talk pricing plan and for the planned end of public template support
• The frequently asked 080 opt-out and Brand Message M·N targeting conditions documented
• Two Sandbox upload and request bugs fixed

What changed?

1. The catalog (FG) type reflected for Kakao Brand Message

Catalog (FG) has been added to the Brand Message types, and it is now reflected not only in the specification but across every screen that handles catalogs.

• msgType FG and headerDescription (FG only, max 36 characters) added to the send and template registration specifications
• The 15 fields of attachment.catalog.list[] and the catalogVariable[] specification added
• FG reflected in the guide message type cards, the Sandbox send form and template editor, and the report message type code table
• Two catalog item image upload APIs added (catalog at 1:1, catalog/oddFirst at 2:1)

2. Brand Message image upload specifications corrected

We compared the docs with the Kakao Biz Message image upload documentation and corrected the values that did not match.

• default: a fixed 0.5 ratio and a 500KB limit → a 0.5–1.333 ratio and a 5MB limit (the previous values were the Alimtalk template specification)
• wide: the recommended size consolidated to a single 800x600
• wideItemList: the minimum width lowered from 500px to 200px
• The two catalog specifications confirmed — catalog recommends 800x800 at a ratio of 1, catalog/oddFirst recommends 800x400 at a ratio of 0.5 with a minimum width of 500px, both capped at 5MB

3. Common file upload request parts applied

File upload uses the same handler regardless of channel, but the documentation listed only file. The optional parts the server actually accepts, and the common constraints, have been filled in.

• fileKey (max 64 characters, generated by the server when omitted) and imageName (the file name without its extension when omitted) added for MMS, RCS, Alimtalk, Brand Message, and CS Talk
• A file name longer than 40 characters returns A201, so the 40-character limit is now stated on the file field

4. CS Talk specification expanded

Items that were only partially documented across the request, receipt, and lookup stages have been filled in.

• KakaoTalk identity verification: the rich bubble type KAKAO_CERT and certExpiry added, along with cert_result on the receiving webhook
• Rich message: the five allowed coupon title formats, the permitted line break counts for message and description, and the per-type button constraints (AL, BF, AC) corrected
• Webhook receipt: attachment is a URL to a txt file containing the full body when the body exceeds 4,000 characters; content is a backward-compatibility field, so use contents for the body; read receipt conditions and the fact that receipt order is not guaranteed have been added

5. Pricing plan and template policy notices

• New CS Talk pricing plan: selecting the plan issues an Omni key, it can be held alongside a communication product plan, and charges are based on the number of channels and chat rooms. This is now in the console guide.
• Public templates: public templates have been removed from the console template selection screen, leaving only the lookup API. If a variable substitution result exceeds the defined character count, the message is not truncated or passed to a fallback — the send fails. That is now called out as a warning, and new integrations are directed to template registration.

6. Frequently asked items documented

• 080 opt-out: numbers blocked through 080 are excluded automatically only for console sends — the exclusion does not apply to API sends. The documentation now states that you must download the list and apply it in your own sending system.
• Brand Message M·N targeting: sending to your own members requires three steps completed in order — applying to switch on Brand Message, registering an 080 toll-free opt-out number, and applying to expand the send audience (subject to Kakao review). M·N appearing disabled in the console and the API returning 628 share the same cause: the third step has not been approved.

7. Sandbox request bugs fixed

• Fixed an issue where multipart upload APIs rendered only the file row and none of the remaining body fields. CS Talk image and file upload always failed with A502 because there was no way to send the required senderKey.
• Fixed APIs that require a wrapper object being sent a flat body.

Why it matters

• If catalog (FG) existed only on the specification page, the type list would differ from screen to screen. Aligning the guide, Sandbox, and report means you see the same type list no matter where you start.
• Mismatched image upload specifications and missing file upload parts surface as failures right at send time. Matching them to what the server actually accepts lets you validate in advance.
• The 080 opt-out and M·N targeting were repeat questions. With the conditions and required actions in the documentation, you can check them during integration.

How to use it

• To send a catalog (FG), first register the item images through the catalog or catalog/oddFirst upload API and put the returned URLs in catalog.list[].imgUrl. With an odd number of items (3, 5, 7) only the first item is 2:1; with an even number (4, 6) all items are 1:1.
• Setting fileKey yourself on upload makes later lookup and management easier. The server generates one when you omit it.
• If you send through the API, download the 080 opt-out list regularly and exclude those numbers from your own send targets.
• If you need Brand Message M·N targeting, first confirm that all three applications have been approved.

Notes

• Catalog (FG) cannot be sent in FriendTalk compatibility mode, and it is not shown on PC or Mac KakaoTalk (visible on KakaoTalk v25.8.0 and later).
• Public template support will end in the future. Use template registration for new integrations.
• The web send limit is 2,000 per month and 300 per day. The console guide previously listed the API key limits here by mistake, and this has been corrected.
• CS Talk channel registration and initial setup are currently handled manually, and support hours and system message settings will become available in stages.