Request access to a published restricted agent

Submit an access request for a published restricted agent. The agent owner / admins can approve or reject via /v1/agents/{agentId}/access/requests/{requestId}.

POST /v1/agents/{agentId}/access/request

Request access to a published restricted agent

cURL

curl --request POST \
  --url https://{host}/v2/workspaces/slug:agent-factory/webhooks/v1/agents/{agentId}/access/request \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "<string>"
}
'

201

{
  "_id": "<string>",
  "agent_id": "<string>",
  "requester_id": "<string>",
  "requester_email": "<string>",
  "orgSlug": "<string>",
  "message": "<string>",
  "resolved_by": "<string>",
  "rejection_reason": "<string>"
}

Authorizations

BearerAuthOrgApiKeyAuth

Authorization · string · header · required

User-bound credential carrying an identity: either a session JWT or a user access token (at:*) generated from the user settings UI. Send as Authorization: Bearer <token>. Org API keys (iak_*) are not accepted here - they carry no user identity. Use the x-prismeai-api-key header instead (see OrgApiKeyAuth).

Path Parameters

agentId · string · required

Maximum string length: 64

Body

application/json

message · string

Optional rationale for the access request.

Maximum string length: 1024

Response

201

application/json

Access request created (pending).

Pending or resolved access request for a restricted agent.

_id · string

agent_id · string

requester_id · string

requester_email · string

orgSlug · string

status · enum<string>

Available options: pending, approved, rejected

message · string

resolved_by · string

rejection_reason · string