Supabase

Overview

The Supabase destination connector lets you authenticate against a Supabase project using the Supabase REST API endpoint. Destination loading is currently still in development, so this connector can validate credentials but does not yet write records.

Setup

1. In Supabase, open your project.
2. Collect:
   • Project ref (the project reference in your Supabase project URL, e.g. https://<project-ref>.supabase.co)
   • API key (a Supabase API key)

Authentication

This connector authenticates by calling your project’s REST endpoint:

• Base URL: https://<project-ref>.supabase.co/rest/v1/
• Header used for validation: apikey: <api-key>

Configuration fields

Field	Type	Required	Description
project_ref	string	Yes	Your Supabase project reference (the subdomain in https://<project-ref>.supabase.co). Must be a valid DNS label: lowercase letters (a-z), digits (0-9), and hyphens (-), 1–63 characters, and cannot start or end with -.
api_key	string	Yes	Supabase API key used to authenticate requests to the REST API.

Streams / Data model

This is a destination connector. Stream selection does not apply.

Limitations

• Loading is not yet supported. Runs will fail at the load step with a message indicating the destination is still in development.
• Credential validation requires network access to https://<project-ref>.supabase.co/rest/v1/.

Troubleshooting

• “Supabase identifier must be a DNS label”: Ensure project_ref is only lowercase letters, digits, and hyphens; is 1–63 characters; and does not start or end with a hyphen.
• “Supabase credential validation failed”: Verify the api_key is correct and has access to the project, and that the project ref matches your project URL.