SuperdindaDocs
Admin

Operators, invited and removed

GET
/admin/members

Authorization

Bearer
headerAuthorizationBearer <JWT>

Response Body

Members

application/json
  1. response
success*true
Value intrue
data*
Example Request
curl -X GET 'http://localhost:3000/admin/members'
Example Response
{  "success": true,  "data": {    "members": [      {        "uid": "string",        "email": "string",        "role": "owner",        "status": "active",        "invitedAt": "string",        "inviteExpiresAt": "string",        "acceptedAt": "string",        "removedAt": "string",        "displayName": "string",        "lastAccessAt": "string",        "invitedBy": {          "uid": "string",          "email": "string",          "displayName": "string"        }      }    ]  }}

Who I am in the backoffice GET

What the screen hides is a convenience; every route checks this again for itself.

Invite an address POST

The invitation lapses in seven days if nobody uses it, and carries `viewer` unless a role is named. No account is created: the address becomes a member when it signs in.