Deprecation rest
Notion deprecated Update agent status (PATCH /v1/agents/{agent_id}/status); send status to Update an agent (PATCH /v1/agents/{agent_id}) instead
What changes
On November 2, 2026, Notion added Update an agent (PATCH /v1/agents/{agent_id}), which changes an agent's name, description, model, status, or favorite state in one request, and deprecated Update agent status (PATCH /v1/agents/{agent_id}/status, notion.agents.updateStatus in @notionhq/client). Callers should send {"status": "active"} or {"status": "disabled"} to Update an agent instead. The request rules are the same, but the response and one error code change. Update agent status returns agent_id, status, and pause_reason; Update an agent returns the full agent object, so read the ID from id. A status change that isn't allowed returns 403 status_change_not_allowed from the old endpoint and 403 restricted_resource from Update an agent. No removal date has been announced.
Deprecation: Still works; removal is announced.
What to do
Replace PATCH /v1/agents/{agent_id}/status with PATCH /v1/agents/{agent_id} and the same {"status": "active"} or {"status": "disabled"} body. @notionhq/client v5.30.0 has no method for Update an agent, so replace notion.agents.updateStatus with notion.request({ method: "patch", path: `agents/${agentId}`, body: { status } }). Read the agent ID from id instead of agent_id in the response, and handle 403 restricted_resource where you handled 403 status_change_not_allowed. Sending "disabled" to an agent that is already disabled, other than through the API, returns 403 restricted_resource and rejects the whole request.
Strings to search for
agents.updateStatus/status