API reference › Members › List members
List members
/v1/membersWho is on this account. There is no CLI command for this endpoint yet.
curl -s https://api.propgate.dev/v1/members \
-H "authorization: Bearer pg_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"{
"data": [
{
"createdAt": "2026-08-01T09:12:44.000Z",
"email": "you@example.com",
"id": "019fcb00-...",
"object": "member"
}
],
"error": null,
"meta": null
}This endpoint is read-only, and deliberately so. A member is added exactly one way — by proving control of a mailbox through the signup flow — because that is the only test of "can act on behalf of this address" that means anything. Removing a member is not offered here because it needs roles first: without them, any member could remove any other, including the founding address that created the tenant in the first place. That is the same gap revoking a key is ungated on today, and it points at the same missing piece rather than something this endpoint can work around.
GET /v1/api-keys already reports the address that created each key in
createdBy — this endpoint is what turns that address into something with a
name on this account: a way to say which addresses on that list are actually
supposed to be there.