Mark a notification as read
Record that you have read one notification.
Marking something read twice keeps the first moment, because that is when it was read. There is no way to mark one unread again: this records something that happened rather than setting a flag.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The address of the notification.
Returns
The notification as it now stands, carrying the moment it was read.
The notification.
Always notification. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
What the notification is about, as a key such as reminder_due or digest. The set grows as the product finds new things to say, so match the keys you care about and let an unfamiliar one through rather than treating it as an error.
Which way it went out: in_app, email, slack, telegram or sms. One notification is written per channel, so a reminder that went out two ways is two records here, alike in everything but this field.
The one line it leads with, up to 255 characters. For a reminder it is the name of the reminder.
What it says under the title, of no fixed length, written in the language the account was set to at the moment it was made rather than the one you are asking in.
When it was due, as a count of seconds since 1970. Quiet hours can hold a notification back, so this can be earlier than sent_at by hours.
When it went out, as a count of seconds since 1970, or null when it has not gone out yet.
When it was first read, as a count of seconds since 1970, or null when it has not been. Reading something twice keeps the first moment.
What the channel said when it refused, up to 255 characters, or null when nothing refused. A notification that failed keeps its record and its reason rather than disappearing.
When the record was written, as a count of seconds since 1970.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.