Settings

Developer Info

Connection details and schema reference for pulling event data into external sites and integrations. Always read through the public_* views — they expose only safe fields from non-archived records and are protected by row-level security. Internal tables stay private.

Connection

Use these with the Supabase JS client, PostgREST, or any HTTP client. The anon key is publishable — RLS does the gating.

Project ref

urnxaxtqewfaluznheam

Project URL

https://urnxaxtqewfaluznheam.supabase.co

REST base URL

https://urnxaxtqewfaluznheam.supabase.co/rest/v1

Realtime URL

wss://urnxaxtqewfaluznheam.supabase.co/realtime/v1

Anon / publishable key

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6InVybnhheHRxZXdmYWx1em5oZWFtIiwicm9sZSI6ImFub24iLCJpYXQiOjE3Nzk3NDk2NDcsImV4cCI6MjA5NTMyNTY0N30.H-c9kqv1yr7FS5BM1JwRVYqcpmP7KVhErgSiswMTSVM

Schema at a glance

How the public views relate. Internal-only tables (registrants, vendors, user_roles) are never exposed.

  public_events
       │
       ├── public_sessions ──┬── public_session_speakers ── public_speakers
       │                     └── public_session_topics ──── public_topics
       │
       └── public_sponsors   (joins event_sponsors + sponsor_profiles)

Security model

What the anon key can and cannot do.

Anon can SELECT from every public_* view. The views filter to non-archived records and project only safe columns.

Anon cannot SELECT the underlying base tables, and cannot INSERT, UPDATE, or DELETE anywhere. All writes happen through the authenticated dashboard.

PII stays internal. Speaker email, registrants, vendors, and user roles are never reachable with the anon key.