- Print
- PDF
AlimTalk Message
- Print
- PDF
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 AlimTalk messages and how to view AlimTalk Message delivery history.
To use features provided in Biz Message > AlimTalk Message, you must have a project set to use the Biz Message. To create a project, see Create project; to edit the settings of a created project, see Edit project.
Send AlimTalk message
You can send an AlimTalk message only through OPEN APIs. See AlimTalk APIs of the Simple & Easy Notification Service API guide.
View AlimTalk message delivery history
To view the AlimTalk message delivery history, follow these steps:
Message delivery history is saved for up to 30 days. If you need to save the data for longer periods, you have to back it up on your own.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Application Services > Simple & Easy Notification Service in order.
- Click Biz Message > AlimTalk Message in order.
- Select the project for viewing the delivery history and the KakaoTalk Channel.
- The AlimTalk 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 AlimTalk APIs.
Export message history
You can export AlimTalk message history to Object Storage.
- Export is only available to Object Storage in the Korea Region and incurs additional charges.
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Application Services > Simple & Easy Notification Service in order.
- Click Biz Message > AlimTalk Message in order.
- Select the project to export message history from and click the [Request export] button.
- The export request popup window appears.
- 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 AlimTalk usage limits
To set AlimTalk usage limits, follow these steps:
- Click the environment you are using in the Region menu and the Platform menu on the NAVER Cloud Platform console.
- Click Services > Application Services > Simple & Easy Notification Service in order.
- Click Biz Message > AlimTalk Message in order.
- Select the project to set usage limits for and click the [Set usage limits] button.
- Set the usage limits and click the [Save] button.
- AlimTalk usage is limited to 30,000 messages per month.
- If you need to send more AlimTalk messages than the monthly limit, contact Customer Support.
- KakaoTalk Biz messages are charged per message sent, with different rates for each message type (AlimTalk, FriendTalk [text, image, and wide formats]).
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.
Starting from the implementation date of link validation, if you can't open a page due to the incorrectly entered or replaced link, even previously successful messages may be marked as failed during the request.
Link failure types
The following are examples of different link failure types that you may find useful for link validation.
Item | Examples |
---|---|
Variables not replaced at all | https://#{variable} |
Variables not replaced correctly | https://{variable} https://www.naver.com{variable} https://https://www.naver.com https://customscheme://customaction |
The starting character of the path is missing or has been encoded | https://search.naver.comsearch?q=test https://search.naver.com%2Fsearch%3Fq%3Dtest |
The domain part is missing or invalid | https://20231016-000001 https://productname https://?q=test https://.naver.com |
localhost | http://localhost:8080 |
Delimiter error between the scheme and the domain (authority) | https:////www.naver.com https:// www.naver.com |
TLD does not exist | https://www.naver.c https://www.naver.comm |