How many items each of the four header trays would show: unread notifications, conversations with unread messages, approvals waiting on you and how many of those are overdue, open sync conflicts, and queued operations needing attention. One row. Intended to be polled in place of re-reading all five lists, so a client can re-read only what has changed. Counts what the caller may see, and nothing a direct select on those views would not already tell them.
Tray
How many items each of the four header trays would show: unread notifications, conversations with unread messages, approvals waiting on you and how many of those are overdue, open sync conflicts, and queued operations needing attention. One row. Intended to be polled in place of re-reading all five lists, so a client can re-read only what has changed. Counts what the caller may see, and nothing a direct select on those views would not already tell them.
POST
How many items each of the four header trays would show: unread notifications, conversations with unread messages, approvals waiting on you and how many of those are overdue, open sync conflicts, and queued operations needing attention. One row. Intended to be polled in place of re-reading all five lists, so a client can re-read only what has changed. Counts what the caller may see, and nothing a direct select on those views would not already tell them.
Headers
Preference
Available options:
params=single-object Body
How many items each of the four header trays would show: unread notifications, conversations with unread messages, approvals waiting on you and how many of those are overdue, open sync conflicts, and queued operations needing attention. One row. Intended to be polled in place of re-reading all five lists, so a client can re-read only what has changed. Counts what the caller may see, and nothing a direct select on those views would not already tell them.
Response
200
OK

