Dry-Run Mode

Append ?dry_run=true only to a supported operation. Authentication, authorization, and applicable request validation still run. A successful dry run does not reserve resources or guarantee that a later real write succeeds.

Supported endpoints

Paths below start with /v1/partnership/accounts/{account_id} unless shown in full.

Path	Method	Dry-run behavior
/marketplacecontrolslists	PUT	Existing validation without saving.
/status	PUT	Existing status validation without saving.
/data-deletion-requests	POST	Validates without submitting account-deletion work.
/layouts/{layout_id}	PATCH	400 DryRunNotSupported, before work.
/pages	POST	400 DryRunNotSupported, before work.
/pages/{page_id}	PUT	400 DryRunNotSupported, before work.
/payout-setup	POST	400 DryRunNotSupported, before work.
/v1/accounts/register/partnership	POST	Unsupported; the flag does not suppress registration.
/v1/partnership/network-privacy-requests	POST	Unsupported; the request is submitted normally.

Do not use the flag as a safety mechanism on any other endpoint. Test layout rendering with real updates on a stage merchant until these previews are available. A dry run is request validation, not browser rendering or a complete end-to-end test.

Supported dry runs bypass the operation cache and do not consume an idempotency key or create a pollable operation. Use an Idempotency-Key for the subsequent real operation.