SSupabaseHelp Center

Guide

Procure Legacy anon, service_role API Keys

3 stepsAgent View (JSON)

Overview

Supabase provides multiple layers of API key management to control how applications access your project's data and services. While modern Supabase projects typically use the anon key (for client-side, row-level security–protected access) and service_role key (for server-side, unrestricted access) available in the standard Connect dialog, legacy API keys remain available in Project Settings for backward compatibility with older integrations or specific use cases. This workflow guides you to the dedicated legacy keys section, which is useful when migrating legacy applications or when you need to explicitly work with older credential formats. Access to these keys requires project owner or administrator permissions.

Before you begin

  • Active Supabase account at supabase.com with login credentials
  • At least one Supabase project created in your account
  • Project owner or administrator role permissions to access Project Settings
  • Active internet connection and access to supabase.com

Step by step

1
ClickProject Settings

Navigate to your project's configuration hub by clicking the Project Settings link in the main navigation. This takes you to the dashboard where all project-wide settings, including API credentials, are managed.

Tip. Project Settings is typically found in the left sidebar of the Supabase dashboard. If you're on a project page, it's usually one of the first links in the navigation menu.
Step 1
2
ClickAPI Keys

Access the API Keys management section by clicking the API Keys menu item. This reveals the credentials panel where all API keys for your project are organized and available for retrieval.

Tip. The API Keys section may be grouped under 'Authentication' or 'Security' depending on your Supabase version. Look for a submenu or expandable section if it's not immediately visible.
Step 2
3
ClickLegacy anon, service_role API keys

Click the Legacy anon, service_role API keys link to access the dedicated legacy credentials page. This displays the older-format API keys that were standard in earlier Supabase versions and remain available for backward compatibility with legacy integrations.

Tip. If you're working with a modern integration, you may find the same keys in the standard Connect dialog or main API Keys overview. The legacy section is specifically for applications that require or prefer the older key format.
Warning. Do not share your service_role API key publicly or commit it to version control. This key has unrestricted access to your database and should only be used in secure, server-side environments.
Step 3

Confirm it worked

  1. 1You are on the Legacy API Keys page within Project Settings, displaying both the legacy anon and service_role key values
  2. 2The page shows a clear header or section title indicating 'Legacy anon, service_role API keys'
  3. 3Both key strings are visible and can be copied to clipboard (typically shown as masked values with reveal/copy buttons)
  4. 4The breadcrumb or navigation path shows: Project Settings > API Keys > Legacy anon, service_role API keys

Common issues

Keep reading

Creating Kubernetes Service Accounts and Kubeconfigs for Anonymization Cluster

Creating Kubernetes Service Accounts and Kubeconfigs for Anonymization Cluster # Creating Kubernetes Service Accounts and Kubeconfigs for Anonymization Cluster Steps to create a Kubernetes service a

docs.protegrity.com

Learn How to Extract a List of Active SAP Concur U... - SAP Community

Learn How to Extract a List of Active SAP Concur U... - SAP Community Enterprise Resource Planning Blog Posts by Members All communityThis categoryBlogKnowledge baseUsersManaged tags cancel Turn on

community.sap.com

ServiceNow Assets Configuration Guide

ServiceNow uses basic authentication with a username and password or token authentication to authenticate requests. This guide walks you through the setup process for both methods. ## Authentication

docs.synqly.com