Skip to main content
Fetch the current deal through the Product API using the user’s OAuth token. Present the counterparty projection, obligations, seller price, timing, evidence, cancellation policy, recurrence, and quote impact. Submit acceptance only after the user explicitly approves the current version. Use an idempotency key and handle funding_required, superseded terms, and overage approval as first-class states. The application cannot approve owner-only wallet actions by itself. Open the Darwin-hosted flow when funding or another first-party confirmation is required. An Application fee is a separate disclosed overlay. It never changes the deal terms Darwin uses for matching or the Network-fee rate.

Product API · Approve Deal

Review the canonical acceptance and authorization workflow.