Skip to content

privy domains configure

Configure an owned HTTP-only cookie domain; DNS setup remains explicit.

Terminal window
privy domains configure [options]
Option Description
--dry-run Validate and print the API request without network access or credentials.
--yes Confirm this mutation or export.
--allow-session-impact Acknowledge that disabling/deleting cookie domains can log out app users.
--body <json> JSON body, or - to read stdin.
--file <path> JSON body file, or - to read stdin.
--cookie-domain <string> Owned DNS hostname, not an origin URL. Normalized to lowercase/ASCII. Changing an existing hostname requires explicit deletion first.
--enabled <boolean> Enable HTTP-only cookies for this domain. Disabling requires --allow-session-impact and may log out app users.
--cookie-same-site-lax <boolean> Explicit app-level SameSite=Lax choice; do not confuse this with dashboard authentication.
--diff Read live state and show changes WITHOUT writing (requires login).
--allow-production Explicitly allow this production mutation; also requires --yes.

Global options such as --app, --account and --profile also apply. See the command reference overview.

Terminal window
privy domains configure --cookie-domain example.com --enabled true --dry-run
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Check environment, current domain and optional same-app web client. No implicit domain replacement or allowed-origin expansion.
  • Production apps: Requires --allow-production and --yes.
  • Verification: Fresh configuration/status read-back. DNS verification is reported separately; an owned DNS domain is required.
  • Retries: None.

Inspect the full contract locally with privy schema domains configure.

Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.