FriendTalk Message

The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

Available in Classic and VPC

This part describes how to send FriendTalk messages and how to view FriendTalk message delivery history.

Send FriendTalk message

You can send a FriendTalk message only through OPEN APIs. See FriendTalk APIs of the Simple & Easy Notification Service API guide.

View FriendTalk message delivery history

To view the FriendTalk message delivery history, follow these steps:

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Application Services > Simple & Easy Notification Service in order.
3. Click Biz Message > FriendTalk Message in order.
4. Select the project for viewing the delivery history and the KakaoTalk Channel.
   • The FriendTalk message delivery history of the messages sent through the selected project and the KakaoTalk Channel will be displayed.
   • If needed, you can set the period or filter the delivery history for viewing the history.
   • Request status: status on delivery requests to the message delivery server
     • Success: request succeeded
     • Failure: request failed
   • Delivery status: status on delivery processing in the message delivery server
     • Success: succeeded in delivery
     • Processing: delivery in progress
     • Failure: failed to deliver
   • SMS failover status: SMS failover status
     • The SMS delivery success status can be checked in SMS message delivery history.
   • Request ID: ID for viewing the individual results through OPEN APIs, which is issued 1 for each receiver
   • Click the [View all results] button to check the results data on the requests for delivery in JSON format.
     • For more information on delivery results data, see FriendTalk APIs.

Export message history

You can export FriendTalk message history to Object Storage.

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Application Services > Simple & Easy Notification Service in order.
3. Click Biz Message > FriendTalk Message in order.
4. Select the project to export message history from and click the [Request export] button.
   • The export request popup window appears.
5. Enter the export information and click the [Request file creation] button.
   • You can select either JSON or CSV as the data transfer format.
   • Enter a file name.
   • Select a target bucket.
     • If no bucket exists, the [Create bucket] button appears. Click it to create a bucket (see Create a bucket)
   • You can check the export request results in [Export list].

Set FriendTalk usage limits

To set FriendTalk usage limits, follow these steps:

1. Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
2. Click Services > Application Services > Simple & Easy Notification Service in order.
3. Click Biz Message > FriendTalk Message in order.
4. Select the project to set usage limits for and click the [Set usage limits] button.
5. Set the usage limits and click the [Save] button.
   • FriendTalk usage is limited to 30,000 messages per month.
   • If you need to send more FriendTalk messages than the monthly limit, contact Customer Support.

Link validation step

Starting April 29, 2024, KakaoTalk, the original service provider, is implementing a link validation step for the "button-direct connection area" to prevent link errors in messages.

Link validation involves proactively checking for cases where the links in the AlimTalk buttons sent to customers cannot be connected properly. The aim is to ensure that when recipients click the button in the AlimTalk they receive, the link opens correctly, not to assess the suitability of the connected page.

Link failure types

The following are examples of different link failure types that you may find useful for link validation.