Available in Classic and VPC
AlimTalk Message describes how to send AlimTalk messages and view AlimTalk message delivery history.
To use the features provided in the Biz Message > AlimTalk Message menu, you must have a project enabled for Biz Message. To create a project, see Create project; to edit the settings of a created project, see Edit project.
Send AlimTalk messages
AlimTalk messages can be sent only through the OPEN API. See AlimTalk APIs in the Simple & Easy Notification Service API guide.
View AlimTalk message delivery history
To view the AlimTalk message delivery history:
Message delivery history can be viewed for up to the last 90 days via the API and console, and the lookup query period can be set up to 30 days.
Since delivery history older than 90 days is not provided separately, you must store and manage downloaded files separately using the Export feature within the available viewing period if necessary.
- In the NAVER Cloud Platform console, navigate to Menu > Services > Application Services > Simple & Easy Notification Service.
- Navigate to Biz Message > AlimTalk Message.
- Select the project and KakaoTalk Channel for which you want to view the delivery history.
- The delivery history of AlimTalk messages delivered through the selected project and KakaoTalk Channel is displayed.
- You can filter the history by setting a time range or applying filters, if needed.
- Request status: The status of the message delivery request to the message delivery server.
- Succeeded: The status when the request is successful.
- Failed: The status when the request has failed.
- Delivery status: The status of the delivery process handled by the message delivery server.
- Succeeded: The status when delivery is successful.
- Processing: The status when delivery is being processed.
- Failed: The status when delivery has failed.
- SMS fallback delivery status: SMS fallback delivery request status.
- The SMS delivery success status can be checked in the SMS message delivery history.
- Request ID: An ID issued per recipient that allows checking individual results via the OPEN API.
- Click [View full result] to check the results data for the delivery request in JSON format.
- For more information about 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 additional charges apply.
- You can only export when the number of requests is 100,000 or fewer.
- In the NAVER Cloud Platform console, navigate to Menu > Services > Application Services > Simple & Easy Notification Service.
- Navigate to Biz Message > AlimTalk Message.
- Select the project to export message history from and click [Request export].
- The export request popup appears.
- Enter the export information and click [Request file creation].
- You can select either JSON or CSV as the data format to transfer.
- Enter the file name.
- Select the destination bucket.
- If no bucket exists, the [Create bucket] button appears; click it to create a bucket (see Create bucket).
- You can check the result of the export request in the [Export list].
Set AlimTalk usage limits
To set AlimTalk usage limits:
- In the NAVER Cloud Platform console, navigate to Menu > Services > Application Services > Simple & Easy Notification Service.
- Navigate to Biz Message > AlimTalk Message.
- Select the project to set usage limits for and click [Set usage limits].
- After setting the usage limits, click [Save].
- AlimTalk usage is limited to a maximum of 30,000 messages per month.
- If you need to send more AlimTalk messages than the monthly limit, please contact Customer Support.
- KakaoTalk Biz Message is billed per message sent, and rates vary by message type (AlimTalk, BrandMessage).
Link validation step
Effective April 29, 2024, KakaoTalk, the original service provider, is implementing a link validation step for the "button-direct connection area" to prevent link errors within messages.
Link validation is the process of proactively checking for cases where links in AlimTalk buttons sent to customers cannot be opened properly. This task is performed to prevent links from failing to open correctly when recipients click them after receiving the AlimTalk, and it does not assess the suitability of the integrated page.
From the effective date of link validation, if a page cannot be opened due to an incorrectly entered or replaced link, the request may fail even for previously successful messages.
Failed link types
The following are examples by failure type that you can reference during link validation:
| Item | Example |
|---|---|
| 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 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 domain (authority). | https:////www.naver.com https:// www.naver.com |
| Non-existent TLD. | https://www.naver.c https://www.naver.comm |