---
title: "List Advisory Members"
method: GET
path: "/api/advisory/members"
tags: ["access"]
---

# List Advisory Members

`GET /api/advisory/members`

## Request

- Base URL: `https://api.flagpost.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.flagpost.ai/api/advisory/members`
- Auth: HTTP bearer

List non-admin advisors in the current advisory.

Intentionally NOT admin-gated. This reads through the RLS-scoped client, and
the advisors SELECT policy ("Advisors can view advisors from their advisory")
already exposes member advisor roster data to every advisor — so
gating here would add no real protection (a member could query the advisors
table directly) while breaking the maintainer add-member flow, which needs
the roster to grant business access. The /settings/members *mutation* path
(update_platform_role) is the one that is admin-gated via require_admin.

## Response `200`

Successful Response

- AdvisoryMemberResponse[]
  - `id` string, uuid, required
  - `email` string, required
  - `full_name` string, required
  - `role` 'admin' | 'member', required
  - `enabled` boolean, required
  - `created_at` string, required

---

[API](https://skmtc.dev/flagpost/apis/flagpost-api.md) - [All operations](https://skmtc.dev/flagpost/apis/flagpost-api/llms.txt) - [OpenAPI document](https://skmtc.dev/flagpost/apis/flagpost-api/revisions/0308cef485ca?raw)