approval_submit and approval_decide

Submits a letter for human approval: checks mandatory details, recipient, data processing agreement and limits, creates the final PDF, calculates the price, reserves the cost and adds an approval to the queue. The embedded card is the preview and approval. Once it appears, a short chat confirmation is enough; PDF links and letter text belong in text-only views. With approval:self_approve, the card shows Approve and Reject. In every other case it opens the signed-in portal. With dryRun, the balance and queue remain untouched.

Input contract

Approves or rejects a pending approval. 'approve' is allowed only when this OAuth connection was explicitly granted the additional approval:self_approve scope. When that scope is absent, the human opens the returned approvalUrl and decides in the signed-in portal. approval:decide is also required. An agent approval dispatches after 10 minutes and can be stopped with order_cancel until then.

Input contract

Contract-shaped example

approval_submit({
  "letterId": "REVIEWED_LETTER_ID",
  "recipientName": "Max Mustermann",
  "recipientStreet": "Musterstrasse",
  "recipientHouseNumber": "1",
  "recipientZip": "10115",
  "recipientCity": "Berlin",
  "clientOrderId": "contract-482-approval-v1",
  "maxCostEuros": 10,
  "reason": "Reviewed contract notice"
})

approval_decide({
  "approvalId": "APPROVAL_ID",
  "decision": "approve",
  "user_saw_preview": true,
  "clientOrderId": "contract-482-decision-v1"
})

Only set user_saw_preview:true after the authorized human saw the preview, exact price, and delivery type. A model statement is not human approval.

For conditional fields and nested object limits, the generated complete tool reference remains authoritative. See errors and safe agent onboarding before implementing retries or a live send.