# Notification flow

Below you can see an example of notification flow for Ledger Entry notifications.

User HTTP response (200 OK) HTTP response (201 Created) GET /notifications/webhooks/ {account}?token=$TOKEN (subscription confirmation request) HTTP response (201 Created) Confirming a subscription* ** Triggering a notification PATCH /twins/{twin}/ledgers/ personal/value (update Ledger Entry request) HTTP response (200 OK) POST /notifications/webhooks (subscription request) User server POST <callback_url> (confirmation request) notification message HTTP response (201 Created) Refreshing a subscription Triggering a notification Removing a subscription* ** *** Triggering a notification Triggering a notification ** Request does not require authorization. *** ’refresh_url’ and ‘unsubscribe_url’ are provided in every notification message. *Request can be sent by user server or user. HTTP response (200 OK) PATCH /twins/{twin}/ledgers/ personal/value (update Ledger Entry request) notification message not sent HTTP response (200 OK) DELETE /notifications/webhooks/ {account}?token=$TOKEN (remove subscription) HTTP response (200 OK) PATCH /notifications/webhooks/ {account}?token=$TOKEN (refresh subscription) HTTP response (200 OK) PATCH /twins/{twin}/ledgers/ personal/value (update Ledger Entry request) HTTP response (201 Created) notification message HTTP response (201 Created) notification message HTTP response (200 OK) PATCH /twins/{twin}/ledgers/ personal/value (update Ledger Entry request) Triggering a notification Confirming a subscription Creating a subscription Trusted Twin API

← Overview →

Was this article helpful?