Auditmark

Get a member by user ID

GET
/members/by-user/{user_id}

Resolve one member by USER id, the identifier every cross-entity reference uses: participants.inspector_user_id, inspections.created_by, assigned_approver_id, approvals and sign-offs. Returns the same MemberRef shape as the members directory on inspection detail, resolved through the same service so the two cannot drift apart.

The path carries by-user on purpose. Plain /members/{user_id} would collide with PATCH /members/{member_id}, which takes the MEMBERSHIP id: OpenAPI treats templated paths differing only in placeholder name as identical, so publishing both makes the /v1 schema invalid for anyone generating a client from it.

Self-lookup is not supported. A field user gets 403 here even for their own id; /me/profile is the self surface.

A member outside the caller's organization is unreadable under RLS and so is indistinguishable from one that does not exist. Both are 404.

Authorization

OrgApiKey
AuthorizationBearer <token>

Organization API key. Send as Authorization: Bearer <key>. Create one in Admin > Settings > API keys.

In: header

Path Parameters

user_id*User Id

Response Body

application/json

application/json

curl -X GET "https://api.auditmark.io/v1/members/by-user/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",  "full_name": "string",  "position": "string",  "role": "string",  "active": true,  "email": "string"}
{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string",      "input": null,      "ctx": {}    }  ]}