API Keys in Supabase

This guide walks you through finding your Supabase project's API keys, and understanding what each one is for.

---

Prerequisites

• Access to your project in the Supabase dashboard (provided as part of your GLBNXT platform).

• At least one table already created in Supabase (see Creating Databases and Vector Databases in Supabase if you haven't done this yet).

---

Steps

Step 1: Find your API keys

1. Open your Supabase dashboard and select your project.

2. In the left sidebar, click Project Settings.

3. Click API Keys.

4. You'll see your two keys: anon public and service_role.

Here's what each one actually means:

• anon key — an "everyday" key. It respects all the access rules (Row Level Security) set up on your tables, so it only ever sees or changes what it's specifically allowed to.

• service_role secret — a "master" key. It skips every access rule entirely and can see or change anything in your database, no exceptions.

💡 Think of it like this: the anon key is a guest pass — it only opens the doors it's been given permission for. The service_role key is a master key to the whole building. Only use it in places you fully trust and control.

---

Handle the service_role key carefully

Because the service_role key bypasses all protections, a few simple rules keep things safe:

• Only use it inside trusted backend tools (like n8n) never inside a website, mobile app, or anything a visitor's browser can see.

• Never paste it into a shared document, chat message, or public workflow export.

---

Need More Information?

If you're not sure which key to use for a particular tool, or want a second pair of eyes before connecting something new to your service_role key, reach out — it's always worth double-checking before wiring up a new integration.

---

Need help? Contact the GLBNXT support team or ask a GLBNXT agent to walk you through the setup.