Accept Invite External Jit Access
Accept an invitation for JIT database access.
Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications
Accept an invitation for JIT database access.
Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co'). Important notes: - Vanity subdomains require a paid plan (Pro/Team/Enterprise) - Usage of vanity subdomains and custom domains is mutually exclusive - After activation, your project's auth services will no longer work on the original {project-ref}.supabase.co hostname - Schedule a downtime window to update client code and OAuth providers before activating
Append data to a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Append data to a signed resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Applies a tracked SQL database migration to a Supabase project, for schema changes or other DDL/DML operations. You can provide a migration name, rollback SQL, and an idempotency key to help prevent duplicate tracking.
Apply or update billing addons and compute instance size. Changes may affect billing; inspect the project plan before modifying addons.
Authorize user-to-role mappings for JIT access.
Requests Supabase OAuth 2.0 authorization for a registered application and returns the redirect location when the endpoint responds with a redirect, or status and error information otherwise.
Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.
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.
Updates network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project. Changes may terminate existing connections that do not match the new rules; the returned status indicates whether the configuration is stored or applied.
Bulk creates secrets for a Supabase project. Secret names must not start with SUPABASE_; leading and trailing whitespace is stripped from names and values before submission.
Deletes one or more secrets from a Supabase project by their names. This action is irreversible - deleted secrets cannot be recovered. Use this action when you need to remove environment variables or configuration secrets that are no longer needed or should be replaced. Supports both single and bulk deletion operations through the same endpoint.
Bulk updates Edge Functions in a Supabase project with configurations such as status and version. The operation can create new functions or replace existing ones; version increments must be supplied manually.
Cancel project restoration.
Checks whether a vanity subdomain is available for a Supabase project without reserving or assigning it. The endpoint requires a Pro, Team, or Enterprise organization plan.
Copy an object. Uses a secret/service-role project key and bypasses Row Level Security.
Counts the number of action runs for a Supabase project using a HEAD request. Use this when you need to retrieve the total count of action runs without fetching the full list of runs.
Count rows from a known exposed table-valued function using HEAD, without a body. PostgREST enforces a read-only transaction; functions attempting database writes fail. Uses an elevated secret/service_role key that bypasses Row Level Security. OAuth requires secrets:read; fine-grained PATs require api_gateway_keys_read and api_gateway_keys_secret_read for project-key discovery. Not for scalar functions.
Count matching rows in an exposed table or view without downloading rows. Uses an elevated secret/service-role key and bypasses Row Level Security. OAuth requires secrets:read; fine-grained personal access tokens require api_gateway_keys_read and api_gateway_keys_secret_read.
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 linked to a Git branch.
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.
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 sent directly.
Creates a new Supabase organization, which serves as a top-level container for projects, billing, and team access.
Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks.
Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
Creates a publishable or secret API key for an existing Supabase project, optionally with a description.
Create a new JWT signing key for a Supabase project, with an optional initial standby or in-use status.
Create a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Create a signed TUS resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Generate a time-limited download capability for an object. Uses privileged project-key discovery; protect the returned URL.
Generate time-limited download capabilities for multiple objects. Uses privileged project-key discovery; protect the returned URLs.
Create a two-hour signed authorization for uploading a Storage object. OAuth connections need ``secrets:read``. Fine-grained personal access tokens need ``api_gateway_keys_read`` and ``api_gateway_keys_secret_read``.
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 a Storage bucket. Uses a secret/service-role project key and bypasses Row Level Security.
Permanently and irreversibly deletes a Supabase project and all associated resources, including databases, storage, and configurations. This action is irreversible — the project cannot be recovered once deleted. Use when you need to completely remove a project from your organization.
Disables preview branching for a Supabase project, which deletes all remaining branches. IMPORTANT: Before calling this endpoint, you must manually delete all non-default branches. The API will reject the request with a 422 error if non-default branches exist. Use this action when you need to completely disable the preview branching feature for a project. This action is irreversible - all branches will be permanently removed and preview branching will be disabled. Requirements: - Preview branching must be enabled on the project - All non-default branches must be deleted first - Project must be on Pro plan or above to have preview branching
Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
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.
Permanently and irreversibly deletes a specific, non-default database branch by its `branch_id`, without affecting other branches.
Delete bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
[Beta] Deletes existing login roles used by the Supabase CLI for the specified project. Use when you need to remove CLI authentication roles that were previously created for project access.
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 the custom domain and requires subsequent updates to client, OAuth, and DNS settings.
Deletes an Edge Function from a Supabase project by its slug. Use this action when you need to permanently remove a deployed Edge Function that is no longer needed or should be replaced. This action is irreversible — the function cannot be recovered once deleted, though you can redeploy it from source if needed.
Delete an external user's JIT invitation.
Delete JIT access by user ID.
Delete a bucket. Uses a secret/service-role project key and bypasses Row Level Security.
Delete a Storage object. Uses a secret/service-role project key and bypasses Row Level Security.
Delete multiple objects. Uses a secret/service-role project key and bypasses Row Level Security.
Permanently delete matching rows from an exposed Supabase table or view. Uses an elevated secret/service_role project key, bypassing Row Level Security. Requires filters unless allow_all_rows explicitly permits an unfiltered delete. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal the project key.
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.
Permanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase URL.
Deploys Edge Functions to a Supabase project using multipart upload.
Disables the preview branching feature for an existing Supabase project, identified by its unique reference ID (`ref`). Note: Preview branching must be enabled on the project for this operation to succeed. If the project does not have preview branching enabled, a 422 error will be returned.
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.
Downloads an object from a private Supabase Storage bucket and returns its bytes as base64 with selected metadata. Choose anon or service-role authorization; anon access requires an allowing storage policy, while service-role access bypasses row-level security. An object version and download filename can optionally be specified.
Retrieve an object from a public bucket.
Retrieve an object using a presigned URL.
Retrieve a Storage object. Uses a secret/service-role project key and bypasses Row Level Security.
Empty a bucket. Uses a secret/service-role project key and bypasses Row Level Security.
Enables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events.
(Beta) Implements the OAuth 2.0 token endpoint to exchange an authorization code or refresh token for access/refresh tokens, based on `grant_type`. This is a standard OAuth 2.0 token endpoint that uses application/x-www-form-urlencoded content type as per OAuth 2.0 specification. Requires a valid registered OAuth application client_id and client_secret. For authorization_code grant type: - Requires valid authorization code obtained from the OAuth authorization flow - Optionally requires code_verifier if PKCE was used during authorization For refresh_token grant type: - Requires valid refresh_token from a previous token exchange
Executes PostgreSQL queries against a Supabase project's database for data retrieval, modification, or schema operations. Read-only mode does not prevent detected INSERT, UPDATE, or DELETE statements from making changes.
Run a read-only SQL query against a Supabase project as supabase_read_only_user. This beta endpoint requires all entity references to be schema-qualified.
Generates and retrieves TypeScript types from a Supabase project's database; any schemas specified in `included_schemas` must exist in the project.
Retrieves detailed information about a specific database branch by its name and project reference. Use this to check branch status, configuration, and metadata before performing operations on the branch.
Retrieves a specific database migration entry from the migration history using its version identifier. Use when you need to inspect migration details, SQL statements, or rollback commands for a specific migration version.
Retrieves a specific SQL snippet by its unique identifier.
Retrieves configuration details for a project's SAML Single Sign-On provider by UUID.
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
Retrieves the execution logs for a specific action run by its ID. Use this to debug action executions, view output messages, and investigate errors that occurred during action runs.
Retrieves the status and details of a specific action run, including its steps, timestamps, and configuration. Use this to monitor or check the progress of an action execution.
Checks the Supabase API for availability, helping diagnose connectivity issues.
Get authenticated image transformation headers. Uses a secret/service-role project key and bypasses Row Level Security.
Retrieve authenticated object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
Retrieve authenticated object information. Uses a secret/service-role project key and bypasses Row Level Security.
Get authenticated object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
Tool to get the list of available regions for creating a new Supabase project. Use when you need to determine which regions are available for project deployment, or to get region recommendations based on geographic location and instance size requirements. Note: This is a Beta endpoint.
Get the project's backup schedule.
Get bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
Get bucket lifecycle response headers. Uses a secret/service-role project key and bypasses Row Level Security.
Fetches the current vanity subdomain configuration for a Supabase project, including its status and any custom domain name. The endpoint requires a Pro, Team, or Enterprise organization plan.
Retrieves the read-only configuration and status for a Supabase database branch, typically for monitoring or verifying its settings.
Get database disk attributes.
Gets database metadata for the given project. Returns information about databases, schemas, and tables structure. Note: This endpoint is deprecated and may be removed in future versions.
Get the project's PostgREST OpenAPI specification.
Get disk utilization.
Fetches comprehensive details for a specific Supabase organization using its unique slug.
Get user-to-role mappings for JIT database access.
Retrieves a Supabase project's just-in-time (JIT) access configuration state using the beta endpoint.
Deprecated by the provider; no sunset date or replacement is announced. Retrieve signing key information for the project's imported JWT secret. The endpoint may return HTTP 404 when unavailable. Behavior is unchanged.
Get organization entitlements.
Retrieves project performance advisors for a Supabase project. Returns a list of performance lints that identify potential issues and optimization opportunities. Note: This endpoint is deprecated.
Get the user's profile.
Retrieves detailed information about a Supabase project by reference ID, including its status, database configuration, organization, region, and creation timestamp. Requires a Management API bearer token with appropriate project read access.
Retrieves details of a specific API key for a Supabase project by its UUID. Use when you need to inspect a single key's configuration, type, or metadata.
Retrieves all API keys for an existing Supabase project, specified by its unique reference ID (`ref`); this is a read-only operation.
Retrieves a Supabase project's authentication settings for read-only inspection, including supported provider configurations, MFA policies, email and SMS templates, security settings, and hooks. The returned configuration may not include every field supplied by the API.
Retrieve a project's consolidated effective database, pooler, Auth, Data API, Realtime, and Storage configuration. This Supabase Management API endpoint is Alpha and currently supports Personal Access Tokens (PATs) only; Supabase OAuth access tokens are not supported.
Get disk autoscale configuration.
Get combined function statistics.
Deprecated by the provider; no sunset date or replacement is announced. Checks whether JWT-based legacy API keys (anon, service_role) are enabled. The endpoint may return HTTP 404 when unavailable. Behavior is unchanged.
Retrieves the unified logs stream for a Supabase project, including database, API, and edge function logs, for monitoring and debugging. Custom queries use ClickHouse SQL against the logs table, filtering by source; legacy source tables and metadata joins must be migrated. Provide both UTC timestamps for a time window; Supabase documents a last-minute fallback without both and a maximum 24-hour range. Check the response's error field even when execution reports success. Returned row fields depend on the query.
Retrieve a Supabase project's Prometheus/OpenMetrics exposition.
Retrieves a Supabase project's network restriction settings, including IPv4 and IPv6 CIDR allowlists, entitlement, and application status. The response may also include the previous configuration while a change is pending.
Retrieves the active PgBouncer configuration (PostgreSQL connection pooler) for a Supabase project, used for performance tuning, auditing, or getting the connection string.
Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`.
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.
Tool to list all signing keys for a Supabase project. Use when you need to retrieve JWT signing keys for authentication verification or rotation management.
Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.
Retrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID.
Checks a Supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade.
Retrieves the latest status of a Supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades.
Get project usage API counts.
Get project usage API request counts.
Retrieves a project's authentication configuration, including provider, MFA, email, SMS, JWT and security settings. The response can contain sensitive secrets.
Retrieves the PostgREST configuration for a specific Supabase project.
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.
Retrieves the current health status for a Supabase project, for specified services or all services if the 'services' list is omitted.
Get public image transformation headers.
Get public object information headers.
Get public object information.
Get Realtime configuration.
Get resumable upload offset and metadata. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Get signed resumable upload offset and metadata. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Retrieves security advisor findings and recommendations for a Supabase project. Use when you need to audit project security posture, identify SQL-based security issues, or get remediation guidance. Note: This endpoint is deprecated and may be removed in future API versions.
Get signed image transformation headers.
Get headers for a presigned object retrieval.
Get bucket details. Uses a secret/service-role project key and bypasses Row Level Security.
Get bucket response headers. Uses a secret/service-role project key and bypasses Row Level Security.
Get bucket-list response headers. Uses a secret/service-role project key and bypasses Row Level Security.
Get project Storage configuration.
Check the Storage service health, distinct from Management API health.
Get Storage service health response headers.
Retrieve object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
Retrieve object information. Uses a secret/service-role project key and bypasses Row Level Security.
Get object information headers. Uses a secret/service-role project key and bypasses Row Level Security.
Retrieve column details, types, primary and unique constraints, and optionally foreign keys for multiple database tables. Some returned metadata uses placeholders, and index information is not fetched.
Handles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions.
Handles OPTIONS request for TUS Resumable uploads to discover server capabilities. Use when preparing resumable upload requests to verify supported TUS protocol versions and extensions.
Insert rows or upsert on primary/UNIQUE keys in an exposed table or view. Uses a secret or service_role project key and bypasses Row Level Security. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal project keys. Upserts can overwrite data.
Invite an external user for JIT database access.
Invoke a known exposed Postgres function with named JSON arguments. Supports custom exposed schemas and table-valued result selection, filters, ordering, pagination, and counts. The function runs with a service-role project key that bypasses Row Level Security and may create, update, or delete data or execute DDL.
Tool to invoke a deployed Supabase Edge Function over HTTPS. Use for testing and debugging Edge Functions with configurable method, headers, body, and authentication.
Invoke a known exposed Postgres function using GET in a read-only transaction. Not an Edge Function or arbitrary SQL executor. Database writes are rejected by PostgREST's GET transaction mode. Uses a secret/service_role key that bypasses Row Level Security, so reads can expose all rows. External side effects of a function are not prevented by a database read-only transaction. Supports table-valued projection, filters, ordering, pagination, and counts. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal project keys.
List one page of action runs for a project.
Retrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies.
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.
Lists metadata for all Edge Functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist.
Lists organizations associated with the authenticated Supabase account, returning their IDs, slugs, and names.
Lists Supabase projects for the authenticated user, including project ID, name, organization ID, region, status, database information, and creation time. OAuth access requires the projects:read scope.
Retrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked.
Lists all configured Single Sign-On (SSO) providers for a Supabase project, requiring the project reference ID (`ref`) of an existing project.
Lists all database branches for a specified Supabase project, providing information about each branch's status, configuration, and metadata. Use this action when you need to view all branches in a project, check branch statuses, or identify available branches before performing operations. Database branches are useful for isolated development and testing of schema changes.
Lists tables and optionally views in Supabase database schemas, providing an overview of database structure. Schema discovery can fall back to public, and per-schema failures are reported alongside any partial results.
List all user-to-role mappings for JIT access.
Retrieves all members of a Supabase organization, identified by its unique slug, including their user ID, username, email, role, and MFA status.
Retrieves the list of applied database migration versions for a Supabase project. Use this to track which migrations have been applied to the project's database. This is a read-only operation that requires the project reference ID.
List one page of projects for an organization.
List billing addons and compute instance selections. Changes may affect billing; inspect the project plan before modifying addons.
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 available restore versions for a project.
Retrieves all secrets (environment variables) for a Supabase project by its reference ID. Use this action when you need to view the secrets configured for a project, such as API keys, database URLs, or other environment variables. Note that secret values in the response may be masked for security reasons.
Retrieves the first page of SQL snippets for the logged-in user, optionally filtered by Supabase project. The response may contain a pagination cursor, but this tool cannot request subsequent pages.
List Storage buckets through the data-plane API. Uses a secret/service-role project key and bypasses Row Level Security.
Search for objects under a prefix. Uses a secret/service-role project key and bypasses Row Level Security.
Search for objects under a prefix using list v2. Uses a secret/service-role project key and bypasses Row Level Security.
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.
Initiates a merge of a database branch into its target database. An optional migration version can limit how far migrations are merged; the response identifies the triggered workflow run.
Modify database disk configuration.
Move an object. Uses a secret/service-role project key and bypasses Row Level Security.
Initiate OAuth authorization to claim a project. Returns redirect responses without following them; continue the browser flow using headers.location. An authorization redirect does not prove the claim has completed.
Send an OPTIONS request to the TUS resumable upload signing endpoint.
Send an OPTIONS request to a TUS resumable upload signing endpoint for a specified path.
[Beta] Patches an existing entry in the project's migration history, updating the name or rollback script. Use this to correct migration metadata after the migration has been created.
Updates project's network restrictions by incrementally adding or removing IPv4/IPv6 CIDR blocks. Use when you need to modify existing restrictions without replacing the entire configuration.
Pause a project, making its services unavailable until it is restored.
Create a TUS upload through the wildcard creation route (an alias of base POST). Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Create a signed TUS upload through the wildcard creation route (an alias of base POST). Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Purge cache for a bucket or its transformations. Uses a secret/service-role project key and bypasses Row Level Security.
Purge cache for an object or its transformations. Uses a secret/service-role project key and bypasses Row Level Security.
Purge cache for the tenant or tenant transformations. Uses a secret/service-role project key and bypasses Row Level Security.
Pushes a database branch, applying migrations and changes to the specified branch. Use when you need to deploy schema changes or migrations to a database branch.
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.
Remove billing addons or revert compute sizing. Changes may affect billing; inspect the project plan before modifying addons.
Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored.
Initiates removal of a specified read replica database from a Supabase project. This beta operation requires a valid replica identifier and permission to manage read replicas; redirect application traffic before removal.
Render an authenticated image with transformations. Uses a secret/service-role project key and bypasses Row Level Security.
Render a public image with transformations.
Render a signed image with transformations.
Replace bucket lifecycle configuration. Uses a secret/service-role project key and bypasses Row Level Security.
Resets an existing Supabase database branch, identified by `branch_id`, to its initial clean state, irreversibly deleting all its current data and schema changes.
Restart a project, temporarily interrupting its services. Newly provisioned projects must wait ten minutes.
Restore a scheduled branch deletion.
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.
Restore the given project.
Retrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug.
Retrieves the body of a specified Supabase Edge Function using its project reference and function slug. This read-only operation does not execute the function or return runtime logs.
Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.
Re-verifies DNS and SSL configurations for an existing custom hostname associated with a Supabase project.
Rollback database migrations and remove them from history.
Select rows from a Supabase/PostgREST table or view, with column selection, filtering, sorting, and pagination. When a project API key is not supplied, the tool may use a service-role key, which bypasses row-level security.
Provisions a read-only replica for a Supabase project in a specified supported AWS region to enhance read performance and reduce latency. This beta feature requires a Pro, Team, or Enterprise organization plan.
Shut down the project Realtime service connections, disconnecting active clients.
Terminate a TUS resumable upload. Uses a secret/service-role project key and bypasses Row Level Security. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Terminate a signed resumable upload. Implements one TUS protocol step; callers retain Location and Upload-Offset for continuation.
Updates an existing Supabase Edge Function's properties, including its name, slug, source code, JWT settings, and import map, using its project reference and function slug.
Updates a Supabase project's configuration (currently supports updating the project name). Use when you need to rename an existing project.
Update the status of an action run.
Updates the description of an existing Supabase project API key without regenerating the key string.
Updates an existing SSO provider's SAML metadata, associated email domains, or attribute mappings for a Supabase project, identified by `ref` and `provider_id`.
Updates an existing Supabase project API key's name, description, or JWT template without regenerating the key. It can request that the key value be revealed in the response.
Update the project's backup schedule.
Updates the configuration of a Supabase database branch, allowing modification of its name, associated Git branch, notification URL, persistence settings, and status. Use this action when you need to modify branch settings after creation, such as linking to a different Git branch, changing the branch name, or updating persistence behavior. Note: Database branching requires a paid Supabase plan (Pro or higher).
Updates a Supabase database branch's configuration, including its name, associated Git branch, persistence, and status. The reset-on-push field is deprecated and ignored by Supabase.
Updates the database password for a Supabase project. Use it to rotate credentials or recover database access.
Updates Supavisor (database pooler) configuration, including default pool size and pool mode, for an existing Supabase project identified by its reference.
Update a user mapping for JIT access.
[Beta] Update a Supabase project's just-in-time (JIT) access configuration. Use to enable or disable JIT access features for privileged operations on the project.
Updates a Supabase project's pgsodium root encryption key. Changing the root key can make data encrypted with the previous key inaccessible.
Deprecated by the provider; no sunset date or replacement is announced. Disable or re-enable JWT-based legacy API keys (anon, service_role). The endpoint may return HTTP 404 when unavailable. Behavior is unchanged.
Update Supabase project Auth configuration via the Management API. Use to fix misconfigured Auth redirects, SMTP settings, or other auth parameters. Only provided fields are updated; others remain unchanged. Before updating, confirm the Auth service status is ACTIVE_HEALTHY by checking project health.
Updates the custom hostname for a Supabase project, requiring subsequent DNS changes for SSL certificate issuance and domain ownership. API errors may be returned in an error message field.
Updates specified PostgreSQL configuration parameters for an existing Supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is advised as incorrect settings can impact stability or require a restart.
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 usage.
Update Realtime configuration.
Updates the SSL enforcement configuration (enable/disable) for a specified Supabase project's database.
Update bucket properties. Uses a secret/service-role project key and bypasses Row Level Security.
Update project Storage configuration.
Update the object at an existing key. Uses a secret/service-role project key and bypasses Row Level Security.
Update matching rows in an exposed Supabase table or updatable view. Uses a secret or service_role project key, bypassing Row Level Security. PostgREST warns that unfiltered PATCH updates every row: filters are required unless allow_all_rows=true. Filters can still match every row; check them carefully. OAuth needs secrets:read; fine-grained PATs need api_gateway_keys_read and api_gateway_keys_secret_read to reveal the project key.
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 `target_version` must be available in the chosen channel.
Upload an object using a presigned URL.
Upload a new object. Uses a secret/service-role project key and bypasses Row Level Security.
Tool to upsert a database migration without applying it. Use when you need to track migration changes for a project. [Beta] This endpoint stores migration metadata without executing the SQL.
The Supabase integration connects your Dench AI CRM directly to Supabase, so agents can read and act on your Supabase data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
235 actions are available for agents to invoke on your behalf. Every call runs through Supabase's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Supabase and click Connect — you'll authorize access through Supabase's own sign-in flow. No API keys or code required.
Ask an agent to use Supabase in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Supabase integration connects your AI CRM to Supabase, so AI agents can work with your Supabase data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Supabase integration currently exposes 235 actions, including Accept Invite External Jit Access, Activate vanity subdomain for project, Append Resumable Upload, Append Resumable Upload Signed, Apply a database migration, and Apply Project Addon. Agents invoke them on your behalf from chat or from automations.
No. You connect Supabase from your Dench workspace using Supabase's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Supabase's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Supabase connection from your workspace settings at any time.