Post provisioning requests decline
Authorizations
JWT Bearer token obtained from authentication. Pass as: Authorization: Bearer
Path Parameters
Provisioning request identifier
1Body
Response
OK
A provisioning request and its current state
Unique provisioning request identifier
Agent the resource would belong to
Agent display name, so the owner knows who is asking
Resource being requested: VAULT (encrypted secret storage for this agent), PHONE_NUMBER (a provisioned number, Starter+ only), or GENERIC (a master-gated operation the agent tried to perform; approving grants permission rather than provisioning anything).
VAULT, PHONE_NUMBER, GENERIC The agent's stated justification
Lifecycle status: PENDING (awaiting the owner), APPROVED (resource provisioned), DECLINED (owner refused — soft, the agent may ask again), EXPIRED (7-day TTL elapsed unanswered), CANCELLED (withdrawn by the agent).
PENDING, APPROVED, DECLINED, EXPIRED, CANCELLED Resource-specific options, if any
What the agent was refused, when this request records a permission rather than a resource
When an unanswered request stops being actionable
When the owner decided; null while PENDING
The owner's note, typically the reason for a decline — surfaced so a second attempt can address the objection instead of repeating the first
Id of what approval created (vault identity or phone identity); null unless APPROVED
When the agent asked
