Connect Supabase to ShipVitals
Projects, API requests, and the plan's and compute's estimated cost
BetaRead-only key · about 2 minutes
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- organizations_read
- Finds the organization the token reads
- organization_admin_read
- Reads the organization's plan for the estimate
- projects_read
- Lists projects and whether each is running or paused
- infra_add_ons_read
- Reads each project's compute size for the estimate
- analytics_usage_read
- Reads each project's API requests a day
Read-only: ShipVitals can't change anything at Supabase.
What ShipVitals keeps: The access token, encrypted, and the organization slug if you enter one.
How to connect
- In Supabase, open Account → Access Tokens.
- Generate a scoped token (a classic token has all of your rights) for your organization with read access to organizations, projects, analytics usage and add-ons, and an expiry you're happy to renew.
- Copy the token. Supabase shows it once.
About 2 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Usage.
Figures it fills
- API requests
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Supabase reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Supabase didn't accept the token: it may have expired or been revoked. Generate a new one in Account → Access Tokens and paste it.
- A permission is missing
- Supabase refused part of the organization's data: the token is missing a read permission. Generate it again with organizations, projects, analytics usage and add-ons read.
- Access removed
- ShipVitals' access was removed in Supabase. Connect it again; the history it brought in is kept.
- Rate-limited
- Supabase is limiting this token's requests (120 a minute, shared with your other tokens). ShipVitals tries again shortly.
- Quota reached
- The account used up a Supabase quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Supabase: renamed, moved or removed. Review the connection's resources, or connect again.
- Supabase is unavailable
- Supabase is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Supabase
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Supabase is reachable.
- An answer ShipVitals didn't expect
- Supabase answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- Supabase needs to know which organization to read: enter its slug, or generate a token scoped to that organization only.