Fetch a member's peer-visible profile attributes
community-directory
Fetch a member's peer-visible profile attributes
Return the target member’s profile-visible attributes as a JSON:API compound document (same shape as the /me/profile-attributes editor read).
Visibility mirrors GET //members/ exactly:
- 401 without a contact JWT; 403 for a banned viewer.
- 404 for unknown hub, a target who has left / has no membership row, hidden profile (non-elevated, non-owner viewer), or missing team_contact — plausible deniability.
- The profile owner always bypasses hide_profile for their own profile; a hard-banned self is blocked earlier by the viewer-ban gate (403) and never reaches this bypass.
- Elevated viewers (owner/admin/moderator) bypass hide_profile for another member’s profile, including active/banned/soft-banned targets.
Only hub configs with is_in_profile=True are returned; soft-deleted definitions are excluded along with their configs (no dangling refs).
GET
Fetch a member's peer-visible profile attributes
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.