Content Notifications consist of a collection of Notifications, where each Notification represents an item of content that has been modified or deleted; and links containing the url to use in retrieving the next set of results, so that you won’t miss any updates.
The notifications generated correspond to FT articles and blog posts (and may include FastFT posts if your licence allows it).
Notification Resource Representation
A notification is represented in the FT API as a JSON data structure, as shown below, that is received in the body of a response. This example shows all possible fields a notification can contain.
The apiUrl to request the content that has been updated
Links Resource Representation
The detail of the next request to make to the Content Notifications API is represented as a link shown below. If you use this link, you should not miss any updates.
The target URI of the link. URIs provided by the notifications API should be considered opaque and not parsed. This will ensure you receive all notifications at least once, and minimises the likelihood of receiving duplicate notifications for a change.
The relationship the target resource has with the notification feed. Currently only next is supported - a link to use for your next request, to ensure you see all notifications. There will only be 1 link of this type.