# Supabase on boxd

> Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications.

- Page: https://boxd.sh/integrations/supabase/
- CLI: `run supabase` (129 commands, 33 marked common)
- SDK: `import { supabase } from "@boxd/run"`; every parameter and response type is at `@boxd/run/supabase`
- Triggers: none
- Connect: `run auth supabase` (Sign in with Supabase), or https://app.boxd.sh/integrations/detail/supabase
- All integrations: https://boxd.sh/integrations/ (Markdown: https://boxd.sh/integrations/index.md)

## From the shell

```sh
run auth supabase      # once: prints a link to connect your account
run supabase           # list its commands
run supabase list-all-projects
```

Parameters are flags (`--flag value`); object and array parameters take a JSON string. Output is YAML, or JSON with `--json`. Calls use your own connection; `--scope <name>` uses a connection shared with your team.

## From a script

```ts
import { every, supabase } from "@boxd/run";

every("1 hour", async () => {
  const result = await supabase.listAllProjects();
  console.log(result);
});
```

Run it with `run supabase.run.ts`. Supabase has no triggers; `every()` polls on a schedule, keeps the script running as a job, and wakes the machine when it is due.

## Commands

Required flags are listed; `run supabase <command> --help` lists the optional ones. "common" marks what `run supabase` shows without `--all`.

| Command | SDK method | Required flags | Optional | Description |
|---|---|---|---|---|
| `alpha-create-api-key` | `supabase.alphaCreateApiKey()` | `--name` `--ref` `--type` | 1 | Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates |
| `alpha-delete-api-key` | `supabase.alphaDeleteApiKey()` | `--id` `--ref` | 0 | Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access |
| `alpha-delete-third-party-auth-integration` | `supabase.alphaDeleteThirdPartyAuthIntegration()` | `--ref` `--tpa-id` | 0 | Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method |
| `alpha-get-third-party-integration` | `supabase.alphaGetThirdPartyIntegration()` | `--ref` `--tpa-id` | 0 | Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref` |
| `alpha-list-third-party-auth-integrations` | `supabase.alphaListThirdPartyAuthIntegrations()` | `--ref` | 0 | Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings |
| `alpha-update-api-key` | `supabase.alphaUpdateApiKey()` | `--id` `--ref` | 1 | Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string |
| `apply-migration` ·common | `supabase.applyMigration()` | `--query` `--ref` | 3 | Apply database migrations to a Supabase project |
| `beta-activate-custom-hostname` | `supabase.betaActivateCustomHostname()` | `--ref` | 0 | Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally |
| `beta-activate-vanity-subdomain` | `supabase.betaActivateVanitySubdomain()` | `--ref` `--vanity-subdomain` | 0 | Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co') |
| `beta-authorize-user-through-oauth` | `supabase.betaAuthorizeUserThroughOauth()` | `--client-id` `--redirect-uri` `--response-type` | 5 | Generates a Supabase OAuth 2.0 authorization URL for user redirection |
| `beta-check-vanity-subdomain-availability` | `supabase.betaCheckVanitySubdomainAvailability()` | `--ref` `--vanity-subdomain` | 0 | Checks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain |
| `beta-create-read-replica` | `supabase.betaCreateReadReplica()` | `--read-replica-region` `--ref` | 0 | Provisions a read-only replica for a Supabase project in a specified, Supabase-supported AWS region to enhance read performance and reduce latency |
| `beta-enable-database-webhooks` | `supabase.betaEnableDatabaseWebhooks()` | `--ref` | 0 | Enables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events |
| `beta-get-project-custom-hostname-config` | `supabase.betaGetProjectCustomHostnameConfig()` | `--ref` | 0 | Retrieves a Supabase project's custom hostname configuration, including its status, SSL certificate, and ownership verification, noting that availability may depend on the project's plan |
| `beta-get-project-network-bans` | `supabase.betaGetProjectNetworkBans()` | `--ref` | 0 | Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation |
| `beta-get-project-network-restrictions` | `supabase.betaGetProjectNetworkRestrictions()` | `--ref` | 0 | Retrieves the network restriction settings (IP allowlists) for a Supabase project |
| `beta-get-project-pgsodium-config` | `supabase.betaGetProjectPgsodiumConfig()` | `--ref` | 0 | Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref` |
| `beta-get-project-ssl-enforcement-config` | `supabase.betaGetProjectSslEnforcementConfig()` | `--ref` | 0 | Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database |
| `beta-get-vanity-subdomain-config` | `supabase.betaGetVanitySubdomainConfig()` | `--ref` | 0 | Fetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference ID |
| `beta-remove-network-bans` | `supabase.betaRemoveNetworkBans()` | `--ipv4-addresses` `--ref` | 0 | Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored |
| `beta-remove-read-replica` | `supabase.betaRemoveReadReplica()` | `--database-identifier` `--ref` | 0 | Remove a read replica from a Supabase project (Pro plan or higher required) |
| `beta-run-sql-query` ·common | `supabase.betaRunSqlQuery()` | `--query` `--ref` | 1 | Executes a given SQL query against the project's database; use for advanced data operations or when standard API endpoints are insufficient, ensuring queries are valid PostgreSQL and sanitized |
| `beta-update-project-network-restrictions` | `supabase.betaUpdateProjectNetworkRestrictions()` | `--ref` | 2 | Updates and applies network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project, which may terminate existing connections not matching the new rules |
| `beta-upgrade-project-postgres-version` | `supabase.betaUpgradeProjectPostgresVersion()` | `--ref` `--release-channel` `--target-version` | 0 | Initiates an asynchronous upgrade of a Supabase project's PostgreSQL database to a specified `target_version` from a selected `release_channel`, returning a `tracking_id` to monitor status; the… |
| `count-action-runs` | `supabase.countActionRuns()` | `--ref` | 0 | Counts the number of action runs for a Supabase project using a HEAD request |
| `create-bulk-secrets` ·common | `supabase.createBulkSecrets()` | `--ref` `--secrets` | 0 | Bulk create secrets for a Supabase project |
| `create-database-branch` | `supabase.createDatabaseBranch()` | `--branch-name` `--ref` | 6 | Creates a new, isolated database branch from an existing Supabase project (identified by `ref`), useful for setting up separate environments like development or testing, which can optionally be… |
| `create-function` ·common | `supabase.createFunction()` | `--body` `--name` `--ref` `--slug` | 4 | Creates a new serverless Edge Function for a Supabase project (identified by `ref`), requiring valid JavaScript/TypeScript in `body` and a project-unique `slug` identifier |
| `create-login-role` | `supabase.createLoginRole()` | `--read-only` `--ref` | 0 | Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks |
| `create-organization` ·common | `supabase.createOrganization()` | `--name` | 0 | Creates a new Supabase organization, which serves as a top-level container for projects, billing, and team access |
| `create-project` ·common | `supabase.createProject()` | `--db-pass` `--name` `--organization-id` `--region` | 6 | Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous |
| `create-project-signing-key` ·common | `supabase.createProjectSigningKey()` | `--algorithm` `--ref` | 1 | Create a new signing key for JWT authentication in a Supabase project |
| `create-sso-provider` | `supabase.createSsoProvider()` | `--ref` `--type` | 4 | Creates a new SAML 2.0 Single Sign-On (SSO) provider for a Supabase project, requiring either `metadata_xml` or `metadata_url` for SAML IdP configuration |
| `create-third-party-auth-integration` | `supabase.createThirdPartyAuthIntegration()` | `--ref` | 2 | Call this to add a new third-party authentication method (OIDC or JWKS) to a Supabase project for integrating external identity providers (e.g., for SSO); the API may also support `custom_jwks` if… |
| `delete-all-branches` | `supabase.deleteAllBranches()` | `--ref` | 0 | Disables preview branching for a Supabase project, which deletes all remaining branches |
| `delete-custom-hostname-config` | `supabase.deleteCustomHostnameConfig()` | `--ref` | 0 | Deletes an active custom hostname configuration for the project identified by `ref`, reverting to the default Supabase-provided hostname; this action immediately makes the project inaccessible via… |
| `delete-database-branch` | `supabase.deleteDatabaseBranch()` | `--branch-id` | 0 | Permanently and irreversibly deletes a specific, non-default database branch by its `branch_id`, without affecting other branches |
| `delete-edge-function` | `supabase.deleteEdgeFunction()` | `--function-slug` `--ref` | 0 | Deletes an Edge Function from a Supabase project by its slug |
| `delete-function` | `supabase.deleteFunction()` | `--function-slug` `--ref` | 0 | Permanently deletes a specific Edge Function (by `function_slug`) from a Supabase project (by `ref`); this action is irreversible and requires prior existence of both project and function |
| `delete-login-roles` | `supabase.deleteLoginRoles()` | `--ref` | 0 | [Beta] Deletes existing login roles used by the Supabase CLI for the specified project |
| `delete-project` ·common | `supabase.deleteProject()` | `--ref` | 0 | Permanently and irreversibly deletes a Supabase project and all associated resources, including databases, storage, and configurations |
| `delete-project-vanity-subdomain` | `supabase.deleteProjectVanitySubdomain()` | `--ref` | 0 | Permanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase URL |
| `delete-secrets` | `supabase.deleteSecrets()` | `--ref` `--secret-names` | 0 | Deletes one or more secrets from a Supabase project by their names |
| `delete-sso-provider` | `supabase.deleteSsoProvider()` | `--provider-id` `--ref` | 0 | Deletes a specific SSO provider by its ID (`provider_id`) from a Supabase project (`ref`), which disables it and returns its details; ensure this action will not inadvertently lock out users |
| `deploy-function` ·common | `supabase.deployFunction()` | `--ref` | 5 | Deploys Edge Functions to a Supabase project using multipart upload |
| `disable-preview-branching` | `supabase.disablePreviewBranching()` | `--ref` | 0 | Disables the preview branching feature for an existing Supabase project, identified by its unique reference ID (`ref`) |
| `disable-project-readonly` | `supabase.disableProjectReadonly()` | `--ref` | 0 | Temporarily disables a Supabase project's read-only mode for 15 minutes to allow write operations (e.g., for maintenance or critical updates), after which it automatically reverts to read-only |
| `exchange-oauth-token` | `supabase.exchangeOauthToken()` | `--client-id` `--client-secret` `--grant-type` | 4 | (Beta) Implements the OAuth 2.0 token endpoint to exchange an authorization code or refresh token for access/refresh tokens, based on `grant_type` |
| `generate-typescript-types` ·common | `supabase.generateTypescriptTypes()` | `--ref` | 1 | Generates and retrieves TypeScript types from a Supabase project's database; any schemas specified in `included_schemas` must exist in the project |
| `get-action-run` | `supabase.getActionRun()` | `--ref` `--run-id` | 0 | Retrieves the status and details of a specific action run, including its steps, timestamps, and configuration |
| `get-action-run-logs` | `supabase.getActionRunLogs()` | `--ref` `--run-id` | 0 | Retrieves the execution logs for a specific action run by its ID |
| `get-auth-config` ·common | `supabase.getAuthConfig()` | `--ref` | 0 | Retrieves the complete authentication configuration for a Supabase project |
| `get-available-regions` | `supabase.getAvailableRegions()` | `--organization-slug` | 2 | Get the list of available regions for creating a new Supabase project |
| `get-branch` | `supabase.getBranch()` | `--name` `--ref` | 0 | Retrieves detailed information about a specific database branch by its name and project reference |
| `get-database-branch-config` | `supabase.getDatabaseBranchConfig()` | `--branch-id` | 0 | Retrieves the read-only configuration and status for a Supabase database branch, typically for monitoring or verifying its settings |
| `get-database-metadata` | `supabase.getDatabaseMetadata()` | `--ref` | 0 | Gets database metadata for the given project |
| `get-function` ·common | `supabase.getFunction()` | `--function-slug` `--ref` | 0 | Retrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug |
| `get-function-body` ·common | `supabase.getFunctionBody()` | `--function-slug` `--ref` | 0 | Retrieves the source code (body) for a specified serverless Edge Function using its project reference and function slug; this is a read-only operation that does not execute the function or return… |
| `get-health` | `supabase.getHealth()` | — | 0 | Check the health status of the Supabase API |
| `get-jit-access-config` | `supabase.getJitAccessConfig()` | `--ref` | 0 | [Beta] Retrieves the project's just-in-time (JIT) access configuration, including user roles and their expiration settings |
| `get-legacy-signing-key` | `supabase.getLegacySigningKey()` | `--ref` | 0 | Retrieves the signing key information for the JWT secret imported as signing key for this project |
| `get-migration` | `supabase.getMigration()` | `--ref` `--version` | 0 | Retrieves a specific database migration entry from the migration history using its version identifier |
| `get-organization` | `supabase.getOrganization()` | `--slug` | 0 | Fetches comprehensive details for a specific Supabase organization using its unique slug |
| `get-performance-advisors` | `supabase.getPerformanceAdvisors()` | `--ref` | 0 | Retrieves project performance advisors for a Supabase project |
| `get-project` ·common | `supabase.getProject()` | `--ref` | 0 | Retrieves detailed information about a specific Supabase project by its unique reference ID |
| `get-project-api-key` | `supabase.getProjectApiKey()` | `--id` `--ref` | 1 | Retrieves details of a specific API key for a Supabase project by its UUID |
| `get-project-api-keys` ·common | `supabase.getProjectApiKeys()` | `--ref` | 1 | Retrieves all API keys for an existing Supabase project, specified by its unique reference ID (`ref`); this is a read-only operation |
| `get-project-legacy-api-keys` | `supabase.getProjectLegacyApiKeys()` | `--ref` | 0 | Checks whether JWT-based legacy API keys (anon, service_role) are enabled for a Supabase project |
| `get-project-logs` ·common | `supabase.getProjectLogs()` | `--ref` | 3 | Retrieves analytics logs for a Supabase project |
| `get-project-pgbouncer-config` | `supabase.getProjectPgbouncerConfig()` | `--ref` | 0 | Retrieves the active PgBouncer configuration (PostgreSQL connection pooler) for a Supabase project, used for performance tuning, auditing, or getting the connection string |
| `get-project-postgres-config` | `supabase.getProjectPostgresConfig()` | `--ref` | 0 | Retrieves the current read-only PostgreSQL database configuration for a specified Supabase project's `ref`, noting that some advanced or security-sensitive details might be omitted from the response |
| `get-project-postgrest-config` | `supabase.getProjectPostgrestConfig()` | `--ref` | 0 | Retrieves the PostgREST configuration for a specific Supabase project |
| `get-project-readonly-mode-status` | `supabase.getProjectReadonlyModeStatus()` | `--ref` | 0 | Retrieves the read-only mode status for a specified Supabase project to check its operational state; this action does not change the read-only state |
| `get-project-signing-keys` ·common | `supabase.getProjectSigningKeys()` | `--ref` | 0 | List all signing keys for a Supabase project |
| `get-project-supavisor-config` | `supabase.getProjectSupavisorConfig()` | `--ref` | 0 | Retrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID |
| `get-project-upgrade-eligibility` | `supabase.getProjectUpgradeEligibility()` | `--ref` | 0 | Checks a Supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade |
| `get-project-upgrade-status` | `supabase.getProjectUpgradeStatus()` | `--ref` | 0 | Retrieves the latest status of a Supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades |
| `get-resumable-upload-base-options` | `supabase.getResumableUploadBaseOptions()` | — | 0 | Handles OPTIONS request for TUS Resumable uploads to discover server capabilities |
| `get-resumable-upload-options` | `supabase.getResumableUploadOptions()` | `--wildcard` | 0 | Handles OPTIONS request for TUS Resumable uploads to discover server capabilities |
| `get-security-advisors` | `supabase.getSecurityAdvisors()` | `--ref` | 1 | Retrieves security advisor findings and recommendations for a Supabase project |
| `get-sql-snippet` | `supabase.getSqlSnippet()` | `--id` | 0 | Retrieves a specific SQL snippet by its unique identifier |
| `get-sso-provider` | `supabase.getSsoProvider()` | `--provider-id` `--ref` | 0 | Retrieves the configuration details for a specific Single Sign-On (SSO) provider (e.g., SAML, Google, GitHub, Azure AD), identified by its UUID, within a Supabase project |
| `get-table-schemas` ·common | `supabase.getTableSchemas()` | `--project-ref` `--table-names` | 3 | Retrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate SQL queries |
| `gets-project-s-auth-config` | `supabase.getsProjectSAuthConfig()` | `--ref` | 0 | Retrieves the project's complete read-only authentication configuration, detailing all settings (e.g., providers, MFA, email/SMS, JWT, security policies) but excluding sensitive secrets |
| `gets-project-s-service-health-status` ·common | `supabase.getsProjectSServiceHealthStatus()` | `--ref` | 1 | Retrieves the current health status for a Supabase project, for specified services or all services if the 'services' list is omitted |
| `handle-resumable-upload-sign-options` | `supabase.handleResumableUploadSignOptions()` | — | 0 | Handles CORS preflight OPTIONS request for TUS resumable upload signing |
| `handle-resumable-upload-sign-options-with-id` | `supabase.handleResumableUploadSignOptionsWithId()` | `--wildcard` | 0 | Handles CORS preflight OPTIONS request for TUS resumable upload signing endpoints |
| `invoke-edge-function` ·common | `supabase.invokeEdgeFunction()` | `--function-slug` `--project-ref` | 5 | Invoke a deployed Supabase Edge Function over HTTPS |
| `list-all-organizations` ·common | `supabase.listAllOrganizations()` | — | 0 | Lists all organizations (ID and name only) associated with the Supabase account, excluding project details within these organizations |
| `list-all-projects` ·common | `supabase.listAllProjects()` | — | 0 | Retrieves a list of all Supabase projects, including their ID, name, region, and status, for the authenticated user |
| `list-backups` | `supabase.listBackups()` | `--ref` | 0 | Lists all database backups for a Supabase project, providing details on existing backups but not creating new ones or performing restores; availability may depend on plan and configuration |
| `list-branches` ·common | `supabase.listBranches()` | `--ref` | 2 | Lists all database branches for a specified Supabase project, providing information about each branch's status, configuration, and metadata |
| `list-buckets` ·common | `supabase.listBuckets()` | `--ref` | 0 | Retrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies |
| `list-database-branches` | `supabase.listDatabaseBranches()` | `--ref` | 0 | Lists all database branches for a specified Supabase project, used for isolated development and testing of schema changes; ensure the project reference ID is valid |
| `list-functions` ·common | `supabase.listFunctions()` | `--ref` | 0 | Lists metadata for all Edge Functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist |
| `list-migration-history` ·common | `supabase.listMigrationHistory()` | `--ref` | 0 | Retrieves the list of applied database migration versions for a Supabase project |
| `list-organization-members` | `supabase.listOrganizationMembers()` | `--slug` | 0 | Retrieves all members of a Supabase organization, identified by its unique slug, including their user ID, username, email, role, and MFA status |
| `list-project-secrets` ·common | `supabase.listProjectSecrets()` | `--ref` | 0 | Retrieves all secrets (environment variables) for a Supabase project by its reference ID |
| `list-secrets` | `supabase.listSecrets()` | `--ref` | 0 | Retrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked |
| `list-sql-snippets` | `supabase.listSqlSnippets()` | — | 1 | Retrieves a list of SQL snippets for the logged-in user, optionally filtered by a specific Supabase project if `project_ref` is provided |
| `list-sso-providers` | `supabase.listSsoProviders()` | `--ref` | 0 | Lists all configured Single Sign-On (SSO) providers for a Supabase project, requiring the project reference ID (`ref`) of an existing project |
| `list-tables` ·common | `supabase.listTables()` | `--project-ref` | 4 | Lists all tables and views in specified database schemas, providing a quick overview of database structure to help identify available tables before fetching detailed schemas |
| `merge-branch` | `supabase.mergeBranch()` | `--branch-id-or-ref` | 1 | Merges a database branch, applying all schema changes and migrations from the branch to the target database |
| `patch-migration` | `supabase.patchMigration()` | `--ref` `--version` | 2 | [Beta] Patches an existing entry in the project's migration history, updating the name or rollback script |
| `patch-network-restrictions` | `supabase.patchNetworkRestrictions()` | `--ref` | 2 | Updates project's network restrictions by incrementally adding or removing IPv4/IPv6 CIDR blocks |
| `push-branch` | `supabase.pushBranch()` | `--branch-id-or-ref` | 1 | Pushes a database branch, applying migrations and changes to the specified branch |
| `reset-database-branch` | `supabase.resetDatabaseBranch()` | `--branch-id` | 0 | Resets an existing Supabase database branch, identified by `branch_id`, to its initial clean state, irreversibly deleting all its current data and schema changes |
| `restore-pitr-backup` | `supabase.restorePitrBackup()` | `--recovery-time-target-unix` `--ref` | 0 | Restores a Supabase project's database to a specific Unix timestamp using Point-in-Time Recovery (PITR), overwriting the current state; requires a paid plan with PITR and physical backups enabled |
| `run-read-only-query` ·common | `supabase.runReadOnlyQuery()` | `--query` `--ref` | 1 | [Beta] Run a SQL query as supabase_read_only_user |
| `select-from-table` | `supabase.selectFromTable()` | `--project-ref` `--select` `--table` | 4 | Select rows from a Supabase/PostgREST table |
| `update-api-key` ·common | `supabase.updateApiKey()` | `--id` `--ref` | 4 | Updates an existing Supabase project API key's metadata including name, description, and JWT template configuration |
| `update-branch` | `supabase.updateBranch()` | `--branch-id-or-ref` | 7 | Updates the configuration of a Supabase database branch, allowing modification of its name, associated Git branch, notification URL, persistence settings, and status |
| `update-database-branch-config` | `supabase.updateDatabaseBranchConfig()` | `--branch-id` | 5 | Updates the configuration of a Supabase database branch, allowing modification of its name, associated Git branch, reset-on-push behavior, persistence, and status |
| `update-database-password` | `supabase.updateDatabasePassword()` | `--password` `--ref` | 0 | Updates the database password for a Supabase project |
| `update-function` ·common | `supabase.updateFunction()` | `--function-slug` `--ref` | 7 | Updates an existing Supabase Edge Function's properties (like name, slug, source code, JWT settings, import map) identified by project `ref` and `function_slug`, supporting plain text code or ESZIP… |
| `update-functions` | `supabase.updateFunctions()` | `--functions` `--ref` | 0 | Bulk update Edge Functions in a Supabase project |
| `update-jit-access-config` | `supabase.updateJitAccessConfig()` | `--ref` `--state` | 0 | [Beta] Update a Supabase project's just-in-time (JIT) access configuration |
| `update-pgsodium-config` | `supabase.updatePgsodiumConfig()` | `--ref` `--root-key` | 0 | Critically updates or initializes a Supabase project's pgsodium root encryption key for security setup or key rotation, requiring secure backup of the new key to prevent irreversible data loss |
| `update-project` ·common | `supabase.updateProject()` | `--name` `--ref` | 0 | Updates a Supabase project's configuration (currently supports updating the project name) |
| `update-project-auth-config` ·common | `supabase.updateProjectAuthConfig()` | `--ref` | 59 | Update Supabase project Auth configuration via the Management API |
| `update-project-custom-hostname` | `supabase.updateProjectCustomHostname()` | `--custom-hostname` `--ref` | 0 | Updates the custom hostname for a Supabase project, requiring subsequent DNS changes to a user-controlled domain for SSL certificate issuance and domain ownership |
| `update-project-legacy-api-keys` | `supabase.updateProjectLegacyApiKeys()` | `--enabled` `--ref` | 0 | Disable or re-enable JWT-based legacy API keys (anon, service_role) for a Supabase project |
| `update-project-postgres-config` | `supabase.updateProjectPostgresConfig()` | `--ref` | 17 | Updates specified PostgreSQL configuration parameters for an existing Supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is… |
| `update-project-postgrest-config` | `supabase.updateProjectPostgrestConfig()` | `--ref` | 4 | Updates PostgREST configuration settings (e.g., `max_rows`, `db_pool`, `db_schema`, `db_extra_search_path`) for a Supabase project to fine-tune API performance, data exposure, and database resource… |
| `update-project-supavisor-config` | `supabase.updateProjectSupavisorConfig()` | `--ref` | 2 | Updates the Supavisor (database pooler) configuration, such as `default_pool_size`, for an existing Supabase project identified by `ref`; the `pool_mode` parameter in the request is deprecated and… |
| `update-ssl-enforcement-config` | `supabase.updateSslEnforcementConfig()` | `--ref` | 1 | Updates the SSL enforcement configuration (enable/disable) for a specified Supabase project's database |
| `update-sso-provider` | `supabase.updateSsoProvider()` | `--provider-id` `--ref` | 4 | Updates an existing SSO provider's SAML metadata, associated email domains, or attribute mappings for a Supabase project, identified by `ref` and `provider_id` |
| `upsert-migration` | `supabase.upsertMigration()` | `--query` `--ref` | 3 | Upsert a database migration without applying it |
| `verify-custom-hostname-dns` | `supabase.verifyCustomHostnameDns()` | `--ref` | 0 | Re-verifies DNS and SSL configurations for an existing custom hostname associated with a Supabase project |

## Docs

- [run CLI](https://docs.boxd.sh/cli/run): Call connected integrations from the shell, connect new ones, and run automations.
- [Quickstart](https://docs.boxd.sh/guides/integrations/quickstart): Connect an integration, call it from the shell, and turn a script into an automation.
- [Connections](https://docs.boxd.sh/guides/integrations/connections): Connect an account once, for yourself or for your whole organization.
- [Scripts](https://docs.boxd.sh/guides/automations/scripts): Typed integrations, triggers, schedules and state in a .run.ts file.
- [Jobs](https://docs.boxd.sh/guides/automations/jobs): How a script becomes a background job: states, retries, sleep and wake.
- [Beyond the catalog](https://docs.boxd.sh/guides/automations/beyond-the-catalog): Reach your own APIs, databases and cloud accounts from a script.