Add allowed projects without replacing an agent's other permissions
POST
/api/agents/{id}/project-accessPersonal API keyConsole session
Add allowed projects without replacing an agent's other permissions.
Requires board access and agents:create in the agent's organization. Accepts 1 to 100 project IDs. Selected projects must be readable and in that organization. Locks the low-trust agent, preserves existing containment, audits new additions, and rejects pending-approval agents or changed trust settings. Repeated additions are idempotent. Saving does not start or retry a task.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Path parameters
idstringRequiredThe agent's id.
Request body
application/json · required
projectIdsarray<string (uuid)>Required
Responses
200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation.
details names each field that failed.401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
Errors return {"error": "..."}, often with a code and details. See errors and limits.