mirror of
https://github.com/supabase/supabase.git
synced 2026-06-21 09:47:20 +08:00
a3b7c8f3a7
* Update parial * Add partial to quickstarts * Auth section * More * Prettier * Realtime * Add soft links to frameworks * Add tab * Fix typo * More changes * Updates * Prettier
17 lines
1.4 KiB
Plaintext
17 lines
1.4 KiB
Plaintext
{/* TODO: How to completely consolidate partials? */}
|
|
|
|
You can also get the Project URL and key from [the project's **Connect** dialog](/dashboard/project/\_?showConnect=true&connectTab={{ .tab }}&framework={{ .framework }}).
|
|
|
|
<Admonition type="note" title="Changes to API keys">
|
|
|
|
Supabase is changing the way keys work to improve project security and developer experience. You can [read the full announcement](https://github.com/orgs/supabase/discussions/29260), but in the transition period, you can use both the current `anon` and `service_role` keys and the new publishable key with the form `sb_publishable_xxx` which will replace the older keys.
|
|
|
|
In most cases, you can get the correct key from [the Project's **Connect** dialog](/dashboard/project/\_?showConnect=true&connectTab={{ .tab }}&framework={{ .framework }}), but if you want a specific key, you can find all keys in [the API Keys section of a Project's Settings page](/dashboard/project/_/settings/api-keys/):
|
|
|
|
- **For legacy keys**, copy the `anon` key for client-side operations and the `service_role` key for server-side operations from the **Legacy API Keys** tab.
|
|
- **For new keys**, open the **API Keys** tab, if you don't have a publishable key already, click **Create new API Keys**, and copy the value from the **Publishable key** section.
|
|
|
|
</Admonition>
|
|
|
|
[Read the API keys docs](/docs/guides/api/api-keys) for a full explanation of all key types and their uses.
|