Skip to content
Evershell Docs

List memberships in an org

GET
/orgs/{id}/memberships
 
curl --request GET \
  --url https://your-org.evershell.ai/v1/orgs/example/memberships \
  --header 'Authorization: Bearer <token>'

Permissions: members:read or members:read:own — callers with the unscoped variant see every membership in the org; callers with only :own see just their own row. All three default roles hold members:read (unscoped); the :own variant is for custom roles that want stricter narrowing.

Path id must match the caller’s org id; cross-org reads return 403 even from an Owner of the other org.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json
object
memberships
Array<object>
object
id
required
string
org_id
required
string
workos_user_id
required

Empty until the invitee accepts and the WorkOS webhook stamps the real id. Use accepted_at to distinguish pending invitations from active members.

string
email
required
string format: email
role
required
string
Allowed values: owner operator member
invited_by
string
invited_at
required
string format: date-time
accepted_at

Null while the invite is still pending.

string format: date-time
Example 
{
  "memberships": [
    {
      "role": "owner"
    }
  ]
}

401

Section titled “401 ”

Missing or invalid credential

Media type application/json
object
error
required
object
code
required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string
message
required

Human-readable summary

string
request_id
required

Server-generated request id for correlating logs

string
details

Optional structured context. Validation errors land at details.fields as a per-field map.

object
key
additional properties
any
Example 
{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}

403

Section titled “403 ”

Caller lacks the required scope, or cross-org access attempted

Media type application/json
object
error
required
object
code
required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string
message
required

Human-readable summary

string
request_id
required

Server-generated request id for correlating logs

string
details

Optional structured context. Validation errors land at details.fields as a per-field map.

object
key
additional properties
any
Example 
{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}