Assign an agent's accountable owner
Makes an active person the agent’s accountable owner and starts a new 90-day review window. Requires permission agents:manage.
v2 compatibility notes
POST /api/v2/agents/assignOwner makes an active person the agent’s accountable owner and starts a new 90-day owner review window. The body is { id, ownerPersonId, expectedOwnerPersonId? }. Send expectedOwnerPersonId (the owner you reviewed, or null for none) to refuse the write with 409 conflict when the agent changed since.
Authority
You needagents:manage at the agent’s home org unit, and agents:read there to see the agent. A missing, PERSONAL, unhomed or unreadable agent is the same 404 resource_missing (Agent not found); an unavailable agent store is 500, never 404. Without agents:manage at the home the answer is 403 permission_denied, recorded as a refused request.
The owner
The person must be active and able to see the agent. An unknown person and one who cannot see the agent get the same400 bad_request, “ownerPersonId must name an active person who can see this agent”, so the route never says whether a person exists. No person id is ever returned.
Replay
With anIdempotency-Key, a repeat of the same request within 24 hours returns the recorded answer only while the slug still names the same agent definition, you may still read the agent at its home, and you still hold the route’s permission there (the agent_write replay rule). Otherwise the repeat is 409 conflict and the write never runs twice.
See Agent accountability.Authorizations
Headers
1–255 printable ASCII characters (0x21–0x7E, no spaces), scoped to the calling credential. A repeat with the same key and request never runs the write again, a 5xx included: once the operation's permissions pass again it answers the identical status and body of the first response (Idempotent-Replayed: true, also sent as Idempotency-Replayed: true), unless the operation's own replay policy withholds it; a first response that was not stored (over 32 KiB, or carrying a one-time secret) answers its first status with only data.id (Idempotency-Replay-Disclosure: id-only) when it named one; otherwise 409 idempotency_result_unavailable; a repeat while the first is still running is 409 idempotency_key_in_flight, and the same key with a different request is 422 idempotency_key_reuse. Honoured for External App JWTs and platform and Personal keys; an External App's static companion key is not protected.
1 - 255
