Request detail — responses & connect
The closing half of the need board: open a posted request, read provider responses (record one from a network partner, mark viewed), then connect with the winner — the request settles to 'connected' — or withdraw it from the board.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: GET /api/v1/demand/needs/:id, POST /api/v1/demand/needs/:id/responses, POST /api/v1/demand/responses/:id/view, POST /api/v1/demand/needs/:id/connect, POST /api/v1/demand/needs/:id/withdraw.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Part of the 'demand' module; board cards link through.
- Who can use it
- RBAC: demand.needs.read (view) / demand.responses.write (record) / demand.needs.write (view-mark, connect, withdraw).
- The API behind it
GET /api/v1/demand/needs/:id, POST /api/v1/demand/needs/:id/responses, POST /api/v1/demand/responses/:id/view, POST /api/v1/demand/needs/:id/connect, POST /api/v1/demand/needs/:id/withdraw- Where it lives
- /demand/[id]/demand
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.