Supabase is an open-source backend platform built on PostgreSQL, providing a database, authentication, storage, and Edge Functions. The Supabase Management API lets you programmatically manage organizations, projects, database branches, Edge Functions, API keys, secrets, and project configuration. Nexla connects to this API to read platform metadata as a source and to provision or update resources as a destination.
Power end-to-end data operations for your Supabase API API with Nexla. Our bi-directional Supabase API connector is purpose-built for Supabase API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Supabase API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Supabase API workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Supabase Management API authenticates with a Personal Access Token (PAT) sent as a Bearer token in the Authorization header. A PAT carries the same privileges as your user account, so keep it secret and store it securely.
Open the Access Tokens page under Account > Access Tokens.
Click Generate new token, enter a descriptive name (for example, Nexla Integration), and generate the token.
Copy the token immediately and store it securely. Supabase displays the token value only once, and it cannot be retrieved again after you leave the page.
Because a Personal Access Token inherits full account privileges, treat it as a sensitive secret. If a token is compromised, revoke it from the Access Tokens page and generate a new one. For details on tokens, scopes, and available operations, see the Supabase Management API reference.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Supabase Personal Access Token in the Personal Access Token field. Nexla sends this value as a Bearer token in the Authorization header on every request to the Supabase Management API.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Supabase API connector tile, then select the credential that will be used to connect to Supabase, and click Next; or, create a new Supabase API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Supabase Management API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Projects
This template ingests data from the Supabase Management API List Projects endpoint. List all projects belonging to the authenticated user.
This endpoint requires no additional parameters and returns data for the authenticated account.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Project
This template ingests data from the Supabase Management API Get Project endpoint. Get a specific project that belongs to the authenticated user.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Organizations
This template ingests data from the Supabase Management API List Organizations endpoint. List all organizations the authenticated user is a member of.
This endpoint requires no additional parameters and returns data for the authenticated account.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Organization
This template ingests data from the Supabase Management API Get Organization endpoint. Get information about an organization.
This endpoint requires the Organization Slug parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Organization Members
This template ingests data from the Supabase Management API List Organization Members endpoint. List members of an organization.
This endpoint requires the Organization Slug parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List API Keys
This template ingests data from the Supabase Management API List API Keys endpoint. Get project API keys.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get API Key
This template ingests data from the Supabase Management API Get API Key endpoint. Get a specific API key for the project.
This endpoint requires the Project Ref and API Key ID parameters. Enter them in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Secrets
This template ingests data from the Supabase Management API List Secrets endpoint. List all secrets for the project.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Functions
This template ingests data from the Supabase Management API List Functions endpoint. List all Edge Functions for the project.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Function
This template ingests data from the Supabase Management API Get Function endpoint. Retrieve an Edge Function.
This endpoint requires the Project Ref and Function Slug parameters. Enter them in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Database Branches
This template ingests data from the Supabase Management API List Database Branches endpoint. List all database branches for the project.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Database Branch
This template ingests data from the Supabase Management API Get Database Branch endpoint. Get a database branch config.
This endpoint requires the Branch ID or Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List SQL Snippets
This template ingests data from the Supabase Management API List SQL Snippets endpoint. List SQL snippets for the logged-in user.
This endpoint requires no additional parameters and returns data for the authenticated account.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get SQL Snippet
This template ingests data from the Supabase Management API Get SQL Snippet endpoint. Get a specific SQL snippet.
This endpoint requires the Snippet ID parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Network Restrictions
This template ingests data from the Supabase Management API Get Network Restrictions endpoint. Get the project's network restrictions.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get SSL Enforcement Config
This template ingests data from the Supabase Management API Get SSL Enforcement Config endpoint. Get the project's SSL enforcement configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Custom Hostname Config
This template ingests data from the Supabase Management API Get Custom Hostname Config endpoint. Get the project's custom hostname configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Auth Config
This template ingests data from the Supabase Management API Get Auth Config endpoint. Get the project's auth configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Postgres Config
This template ingests data from the Supabase Management API Get Postgres Config endpoint. Get the project's Postgres configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Pooler Config
This template ingests data from the Supabase Management API Get Pooler Config endpoint. Get the project's Supavisor (connection pooler) configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Storage Config
This template ingests data from the Supabase Management API Get Storage Config endpoint. Get the project's storage configuration.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Database Migrations
This template ingests data from the Supabase Management API List Database Migrations endpoint. List applied migration versions for the project.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Generate TypeScript Types
This template ingests data from the Supabase Management API Generate TypeScript Types endpoint. Generate TypeScript types from the project's database schema.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List Backups
This template ingests data from the Supabase Management API List Backups endpoint. List all backups for the project's database.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Project Health
This template ingests data from the Supabase Management API Get Project Health endpoint. Get the project's service health status.
This endpoint requires the Project Ref and Services parameters. Enter them in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Performance Advisors
This template ingests data from the Supabase Management API Get Performance Advisors endpoint. Get the project's performance advisor lints.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Security Advisors
This template ingests data from the Supabase Management API Get Security Advisors endpoint. Get the project's security advisor lints.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] List SSO Providers
This template ingests data from the Supabase Management API List SSO Providers endpoint. List all SSO providers configured for the project.
This endpoint requires the Project Ref parameter. Enter it in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get SSO Provider
This template ingests data from the Supabase Management API Get SSO Provider endpoint. Get an SSO provider by its UUID.
This endpoint requires the Project Ref and Provider ID parameters. Enter them in the endpoint configuration before testing the source.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
[Rest API] Get Profile
This template ingests data from the Supabase Management API Get Profile endpoint. Get the authenticated user's profile.
This endpoint requires no additional parameters and returns data for the authenticated account.
This endpoint reads from the Supabase Management API. For response fields, path parameters, and usage details, see the Supabase Management API reference.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Supabase API data sources can also be manually configured to ingest data from any valid Supabase Management API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Supabase API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Supabase destination, and select the Send to Destination option from the menu. Select the Supabase API connector from the list of available destination connectors, then select the credential that will be used to connect to Supabase, and click Next; or, create a new Supabase API credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Supabase Management API endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create Project
This template sends Nexset records to the Supabase Management API Create Project endpoint. Create a new Supabase project.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Delete Project
This template sends Nexset records to the Supabase Management API Delete Project endpoint. Delete a project.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record triggers a separate DELETE request. No request body is sent for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Create Organization
This template sends Nexset records to the Supabase Management API Create Organization endpoint. Create a new organization.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Create API Key
This template sends Nexset records to the Supabase Management API Create API Key endpoint. Create a new API key for the project.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Delete API Key
This template sends Nexset records to the Supabase Management API Delete API Key endpoint. Delete an API key for the project.
This endpoint requires the Project Ref and API Key ID parameters, supplied in the endpoint configuration.
Each Nexset record triggers a separate DELETE request. No request body is sent for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Create Secrets
This template sends Nexset records to the Supabase Management API Create Secrets endpoint. Bulk create secrets for the project.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Create Function
This template sends Nexset records to the Supabase Management API Create Function endpoint. Create a new Edge Function.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Update Function
This template sends Nexset records to the Supabase Management API Update Function endpoint. Update an Edge Function.
This endpoint requires the Project Ref and Function Slug parameters, supplied in the endpoint configuration.
Each Nexset record is sent as a separate PATCH request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Create Database Branch
This template sends Nexset records to the Supabase Management API Create Database Branch endpoint. Create a new database branch for the project.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record is sent as a separate POST request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
[Rest API] Update Auth Config
This template sends Nexset records to the Supabase Management API Update Auth Config endpoint. Update the project's auth configuration.
This endpoint requires the Project Ref parameter, supplied in the endpoint configuration.
Each Nexset record is sent as a separate PATCH request with the record serialized as the JSON request body. Match your Nexset fields to the request schema the Supabase Management API expects for this operation.
This endpoint writes to the Supabase Management API. For the required request body schema and field definitions, see the Supabase Management API reference.
Supabase API destinations can also be manually configured to send data to any valid Supabase Management API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Supabase Management API expects JSON request bodies for create and update operations. Ensure each Nexset record matches the schema the target endpoint requires, and include any path identifiers (such as the project ref) in the endpoint configuration.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Supabase endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Supabase endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
