API Reference
The Onoots Proptech API. HTTPS, JSON request and response. Every endpoint (except the
public listings routes) requires Authorization: Bearer <jwt> and is scoped to your
brokerage by row-level security (RLS).
API groups
| Group | Description |
|---|---|
| Authentication | Bearer tokens (Supabase), roles, and RLS |
| Leads | Create, claim, and convert leads |
| Listings | Public and dashboard listings · ask-agent |
| Deals | Deal pipeline |
| Compliance | Document upload and approval |
| Earnings & Cap | Commissions, cap, and equity |
| Brokerage Admin | Brokerage settings |
| Buyer Desk | Buyer briefs + gates (bilateral marketplace) |
| Read API | Read-only tools (MCP) |
Conventions
- Authentication —
Authorization: Bearer <jwt>(see Authentication). - Errors — JSON with an
errorfield + the matching HTTP status. - Pagination —
page/per_pagewhere applicable. - Scope — RLS scopes every response to your role and brokerage.
Last updated on