Mark notifications as unread

post

https://app.asana.com/api/1.0/users/{user_gid}/notifications/markUnread

Required scope: notifications:write

Marks only the given notifications as unread for the authenticated user. A notification that is archived is also unarchived and moves to the top of Inbox, matching the Inbox UI's unarchive action. Notifications already in Inbox keep their existing position. A user may only mark their own notifications. GIDs that don't exist, don't belong to the caller, or have been deleted are reported in failed_gids rather than failing the whole request.

Path Params

user_gid

string

required

A string identifying a user. This can either be the string "me", an email, or the gid of a user.

Query Params

opt_fields

array of strings

This endpoint returns a resource which excludes some properties by default. To include those optional properties, set this query parameter to a comma-separated list of the properties you wish to include. Properties can include nested fields. To learn more, see the input/output options guide.

opt_fields

Allowed:

opt_pretty

boolean

Provides “pretty” output.
Provides the response in a “pretty” format. In the case of JSON this means doing proper line breaking and indentation to make it readable. This will take extra time and increase the response size so it is advisable only to use this during debugging.

Body Params

data

object

required

Responses

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successfully processed the request. Check failed_gids for any notifications that could not be updated.

400This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again.

401A valid authentication token was not provided with the request, so the API could not associate a user with the request.

403The authentication and request syntax was valid but the server is refusing to complete the request. This can happen if you try to read or write to objects or properties that the user does not have access to.

404Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.

500There was a problem on Asana’s end. In the event of a server error the response body should contain an error phrase. These phrases can be used by Asana support to quickly look up the incident that caused the server error. Some errors are due to server load, and will not supply an error phrase.