notifications
4 endpoints.
One of the two paged endpoints. Keep requesting while nextCursor is set: it is what tells you a feed has more behind it, and a page shorter than the limit can still have a cursor, because the cursor comes from the last row fetched rather than the last one that survived filtering.
get/api/notifications#
limitintegercursorstringstatusstringallunreadcurl https://api.shairelabs.com/api/notifications \
-H "Authorization: Bearer $SHAIRE_TOKEN"itemsobject[]*[item]objectidstring · uuid*typestring*assignedcommentedmentionedentityobject*typestring*ticketpagemilestonelistidstring · uuid*titlestring*subtitlestring | null*keystring | null*listIdstring · uuid | null*statusIdstring · uuid | null*iconstring | null*glyphstring | null*subjectTypestring*ticketmilestonepageactorobject | null*idstring · uuid*namestring*payloadobject*[key: string]unknownreadAtstring | null*createdAtstring*nextCursorstring | null*post/api/notifications/read#
ids(string · uuid)[]*curl https://api.shairelabs.com/api/notifications/read \
-X POST \
-H "Authorization: Bearer $SHAIRE_TOKEN" \
-H "Content-Type: application/json" \
-d '{"ids":[]}'post/api/notifications/read-all#
curl https://api.shairelabs.com/api/notifications/read-all \
-X POST \
-H "Authorization: Bearer $SHAIRE_TOKEN"get/api/notifications/unread-count#
curl https://api.shairelabs.com/api/notifications/unread-count \
-H "Authorization: Bearer $SHAIRE_TOKEN"countinteger*