# Webhook delivery completion event
Only corporate users who have submitted the required applications can use the functions described in this document. To use these functions with your LINE Official Account, contact your sales representative or contact our Sales partners (opens new window).
# Overview of webhook delivery completion events
When a request is made to the LINE notification messages API and delivery of the LINE notification message to the user is completed, a dedicated webhook event (delivery completion event) is sent from the LINE Platform to the webhook URL of the bot server.
- Webhook delivery completion event specifications
- Additional information on webhook delivery completion events
# Webhook delivery completion event specifications
| Property name | Type | Description |
|---|---|---|
| type | String | delivery |
| mode | Object | See Common properties. |
| source | Object | See Common properties. |
| timestamp | Number | See Common properties. |
| webhookEventId | String | See Common properties. |
| deliveryContext | Object | See Common properties. |
| delivery | Object | A delivery object containing a hashed phone number string or a string specified by X-Line-Delivery-Tag. |
| delivery.data | String | A hashed phone number string or a string specified by X-Line-Delivery-Tag. |
Example webhook event
The webhook delivery completion event indicates that the LINE notification message has been delivered to the user and the message can now be viewed. It doesn't indicate the following:
- Successful LINE notification messages API request
- User gets "Set up to get LINE notification messages" message
- Consent to get LINE notification messages
- User gets a message asking for SMS authentication
- User performs SMS authentication
- User opens the LINE notification message (read)
Use the channel secret for Verifying signatures upon receipt of the delivery completion event. For channels using LINE Chat Plus, use Switcher Secret to verify signatures.
# Additional information on Webhook delivery completion events
Even if a LINE notification messages API request is sent and a response is made with the HTTP status code 200, depending on the user's LINE notification message reception settings and SMS authentication status, LINE notification messages may not be delivered to the user or the sending of LINE notification messages may be suspended.
If a LINE notification messages API request is sent and a Webhook delivery completion event isn't received within 24 hours after the response is made with the HTTP status code 200, it means that the LINE notification message wasn't delivered to the user for one of these reasons.
- The user has blocked the LINE Official Account
- The user didn't give required consent or authentication
# The user has blocked the LINE Official Account
Even if the user has blocked the LINE Official Account that sent the LINE notification message, requests for the LINE notification messages API will be responded with HTTP status code 200.
# The user didn't give required consent or authentication
It's possible that the settings for receiving LINE notification messages haven't been set, or that SMS authentication is required, but these settings or operations haven't been performed. For more information, see When the LINE notification messages API request is successful but the message isn't sent.