Developers

The read-only public data surface behind every public Dealora page -- documented for anyone building their own integration against it.

What this is

Every public page on Dealora -- Browse Presences, Browse Posts, public Presence profiles, Discover -- is built entirely from a small set of read-only, RLS-safe views. Nothing about these views is private or internal: they are the exact same rows your browser already fetches when you visit the site signed out. This page documents them so anyone can build their own read-only integration against the same data, through the standard Supabase/PostgREST read API, with an anonymous key.

There is no separate developer credential to request and no rate-limited paid tier -- this is the same public surface for everyone, always free, matching every other free capability on Dealora during the current free-launch period.

Public views

public_stores

Used by: Browse Presences, public Presence profile pages

Every publicly visible Presence (entity) -- name, type, verification, category, capabilities, and profile content. Never includes private contact details or internal-only fields.

id, display_name, type, country, verification_status, verification_level, store_description, headline, logo_url, banner_url, category, capabilities, languages, website_url, handle

public_listings

Used by: Browse Posts, sector/category pages, public Presence profiles

Every publicly listed Opportunity, joined with a public-safe snapshot of its author (individual or Presence). Confidential fields (exact contact details, private negotiation state) are never included.

id, title, description, opportunity_type, store_display_name, store_type, store_verification_status, category, location, budget_range, urgency, created_at

public_posts

Used by: Discover, Pulse Visual, public Presence profiles

Every publicly published Post, with the same author-identity resolution rules as public_listings.

id, post_type, body, category, location, tags, author_display_name, author_type, author_verification_status, created_at

public_media

Used by: Showcase galleries, Pulse Visual, public Presence profiles

Media explicitly marked for public preview, and only for an Opportunity, Presence, or Post that is itself already public.

id, opportunity_id, entity_id, post_id, media_type, url, category, caption, created_at

public_participants

Used by: Discover, Network suggestions

Discoverable individuals and Presences that have opted into discovery and are not in a restrictive governance state.

participant_id, kind, display_name, avatar_url, bio, created_at

public_team_members

Used by: Public Presence profile Team section

Members of a public Presence who have personally opted in to public listing (a member’s own consent, not their owner/admin’s).

entity_id, user_id, display_name, member_role, created_at

public_live_sessions

Used by: Live Sessions

Scheduled or live public sessions, when the Live Sessions feature is enabled for the caller.

id, entity_id, title, description, scheduled_at, status, host_display_name, host_type, host_verification_status, opportunity_title

public_official_announcements

Used by: Official Channel

Published announcements from Dealora’s own Official Channel, when that feature is enabled.

id, kind, title, body, pinned, created_at

public_official_channels

Used by: Site footer, Official Channel

Dealora’s own official external channels (social, messaging).

platform, label, url, handle, sort_order

Not offered (yet)

Outbound webhooks, API keys, and OAuth app connectors are not available. Shipping any of those responsibly needs a real security design -- an outbound-fetch surface hardened against SSRF, a signed and rate-limited delivery log, and a credential-revocation story -- rather than an incremental addition. If you need your own data (opportunities, listings, deal-room membership) in bulk, export it directly from the relevant page in your account.