Update notification state

PATCH/v1/notifications/{notificationId}

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
notificationIdpathstringYes—
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
seenbooleanNo—
readbooleanNo—
dismissedbooleanNo—
archivedbooleanNo—
bookmarkedbooleanNoMark or unmark this notification without changing its read or decision state. Explicit dismissal remains available.
actedbooleanNo—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Updated notificationapplication/json
FieldTypeRequiredDescription
notificationobjectYes—
notification.contextobjectNo—
notification.context.permissionRequestobjectNoOriginal proposed action, returned only by a notification detail read with current thread read access. Retained after approval or denial. Decision status and resolvedBy identity are projected into metadata.decision on the existing inbox item.
notification.context.permissionRequest.requestIdstringYes—
notification.context.permissionRequest.toolNamestringYes—
notification.context.permissionRequest.inputstringYes—
notification.context.permissionRequest.reasonstringNo—
notification.context.permissionRequest.permissionRing1 | 2 | 3No—
notification.context.permissionRequest.permissionRingLabelstringNo—
notification.context.permissionRequest.permissionActionLabelstringNo—
notification.context.userMessagestringNo—
notification.context.runSummarystringNo—
notification.context.requesterIdstringNo—
notification.context.requesterNamestringNo—
notification.context.requesterAvatarUrlstringNo—
notification.context.agentNamestringNo—
notification.context.agentAvatarUrlstringNo—
notification.context.actorNamestringNo—
notification.context.actorAvatarUrlstringNo—
notification.context.computerNamestringNo—
notification.context.threadIdstringNoThread ID.
notification.context.workflowIdstringNo—
notification.context.runIdstringNo—
notification.context.resourcesobject[]No—
notification.context.resources[].idstringYesUnique identifier.
notification.context.resources[].namestringYesHuman-readable name.
notification.context.resources[].resourceTypestringYes—
notification.context.resources[].mutationVerbcreated | updatedNo—
notification.idstringYesUnique identifier.
notification.eventIdstringYes—
notification.eventTypestringYes—
notification.recipientUserIdstringYes—
notification.organizationIdstringNo—
notification.preferenceKeyagentRuns | permissionRequests | assignedWork | taskActivity | invitations | productUpdatesYes—
notification.categoryagent_runs | permission_requests | assigned_work | task_activity | invitations | product_updatesYes—
notification.severityinfo | success | warning | error | criticalYes—
notification.titlestringYesDisplay title.
notification.bodystringYes—
notification.actionUrlstringNo—
notification.resourceTypestringNo—
notification.resourceIdstringNo—
notification.metadataobjectYesFree-form metadata object.
notification.seenAtstringNo—
notification.readAtstringNo—
notification.dismissedAtstringNo—
notification.archivedAtstringNo—
notification.bookmarkedAtstringNoRecipient bookmark timestamp. Bookmarked notifications remain in Inbox when read items are automatically removed.
notification.actedAtstringNo—
notification.createdAtstringYesISO 8601 timestamp.
notification.updatedAtstringYesISO 8601 timestamp.
400No supported state supplied
None.
401Authentication required
None.
404Notification not found
None.
Update notification state
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow