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:
Message delivery history is saved for up to 30 days. If you need to save the data for a longer period, you have to back it up separately.
- In the NAVER Cloud Platform console, navigate to
> 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 AlimTalk message delivery history of the messages sent through the selected project and the KakaoTalk Channel will be displayed.
- You can filter the history by setting a time range or applying filters, if needed.
- Requests status: The status of the message delivery request to the message server.
- Succeeded: Successful request status.
- Failed: Failed request status.
- Delivery status: The status of the delivery process handled by the message server.
- Succeeded: Successful delivery status.
- In process: Message processing status.
- Failed: Failed delivery status.
- SMS fallback delivery status: SMS fallback delivery request status.
- The SMS delivery success status can be checked in SMS message delivery history.
- Request ID: An ID that allows you to check individual results via the OPEN API. One ID is issued per recipient.
- Click [View full result] to check the results data on the requests for delivery 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 up to 100,000 requests at a time.
- In the NAVER Cloud Platform console, navigate to
> 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 JSON or CSV as the data transmission format.
- 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 a 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
> 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].
- Set the usage limits and click [Save].
- 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, BrandMessage).
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.
Failed link types
The following are examples of different link failure types that you may find useful for 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 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 |