A person approves an agent action by email or SMS link; no OneShot account needed. Without a policy, connected-system writes require approval.
Action policy
tool, when conditions and action (require_approval or deny). All conditions must hold; deny wins.
tool: email, sms, voice, commerce, physical_mail, practice_appointments_book, crm_notes_create, crm_contacts_upsert, crm_deals_update, crm_tasks_create, linkedin_invite, linkedin_invite_withdraw, linkedin_react, linkedin_reply, linkedin_message, build, browser, identity, or *.
Checked on every paid route with an outside side effect, after pricing and before payment settles or credit is debited.
linkedin/profile-view and linkedin/sync are not gated. For build and browser, the rule sees what the quote will run, not the request body. A wallet session sets the policy; an access token can only read it.
When a call is held
403; nothing is sent or charged:
X-Approval-Id. An approval releases only the action it was granted for (same recipients, content, product and quantity), within 24 hours of the decision; a second use returns 409 approval_already_used; a released call that fails before dispatch restores it.
A denied call returns 403 action_denied_by_policy with the rule id. The SDKs raise ApprovalRequiredError and ActionDeniedError.
Asking directly
What the approver sees
Summary, preview, Approve / Deny with an optional note. Opening the link decides nothing; each link works once and expires at the deadline. Unanswered means denied.Compute goals
With an approver set, a compute goal’shuman_approval task also goes to them; their decision resolves it like POST /v1/compute/:goalId/respond, and an answer through /respond first disables the link.
Receipts
Every decision, expiry or cancellation writes a signed$0 receipt (approval subcategory): a digest of who was asked and what they saw, the decision, when and how. A released call carries approvalId in its receipt metadata.