Members and invitations
List members and invitations, invite people, change a member's role or permissions and remove members with the AbuseZero REST API.
Members are the people in a workspace. Each workspace has one owner. Admins hold every permission except the owner's. Developers and viewers hold the permissions granted to them. The same members appear in Workspace settings → Members & access.
Listing needs operations:general. Inviting, changing and removing members needs operations:management and a member's own OAuth sign-in, such as the AbuseZero CLI, because who may change whom follows that member's role, exactly as in the dashboard:
- Only the owner and admins manage members.
- Only the owner invites, promotes, demotes or removes admins.
- Nobody changes their own access, and the owner's access never changes here.
A machine client gets MEMBER_SIGN_IN_REQUIRED for these changes. An API key gets KEY_PERMISSION_DENIED, because they need operations:management. Ownership transfers stay in the dashboard (see Exclusions).
The member object
{
"object": "member",
"id": "41958302746610938471",
"name": "Priya Shah",
"email": "priya@example.com",
"role": "developer",
"permissions": ["publish", "keys"],
"invited_at": "2026-11-01T09:00:00.000Z",
"joined_at": "2026-11-01T10:00:00.000Z",
"last_sign_in_at": "2026-11-10T09:00:00.000Z",
"you": false
}| Field | Type | Description |
|---|---|---|
object | "member" | The object type. |
id | string | The member's user ID. |
name | string or null | The member's name. |
email | string | The member's email address. A signed-in member without Reveal personal identifiers sees other members' addresses partly hidden, as in the dashboard. |
role | owner, admin, developer or viewer | The member's role. |
permissions | array of strings | A developer's or viewer's permissions. Empty for the owner and admins, who hold every permission by role. |
invited_at | string or null | When the member was invited. null for the owner. |
joined_at | string or null | When they accepted the invitation. |
last_sign_in_at | string or null | When the member last signed in. |
you | boolean | Whether this is the signed-in member. |
Permissions
| Value | Dashboard label |
|---|---|
manage | Manage integrations, lists, and imports |
publish | Publish policies and benefits |
keys | Create and revoke keys |
reveal | Reveal personal identifiers |
export | Export data |
delete | Delete matching history |
List members
Returns the workspace's members: the owner first, then admins, developers and viewers.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
GET | /v1/members | operations:general | Not used |
Also available as abusezero members list in the AbuseZero CLI, abusezero_list_members on the AbuseZero MCP server and members() in the AbuseZero Node.js SDK.
Query parameters
| Parameter | Type | Required | Limits | Description |
|---|---|---|---|---|
limit | integer | No | 1 to 100, default 50 | How many members to return. |
cursor | string | No | The next_cursor from the previous page, unchanged. |
Response
Returns 200 with a list of member objects.
Update a member
Changes a member's role, permissions or both. Send at least one. Reducing someone's access needs no typed confirmation here: the operations:management scope is the permission.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
PATCH | /v1/members/{id} | operations:management | Required |
Also available as abusezero members update in the AbuseZero CLI, abusezero_update_member on the AbuseZero MCP server and updateMember() in the AbuseZero Node.js SDK.
- The member's new access applies to their next request, in the dashboard and in every app they authorized.
- The member gets an email when their access changes.
- Making someone the owner is an ownership transfer, which stays in the dashboard.
Body parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
role | admin, developer or viewer | No | The member's new role. Only the owner chooses admin, or changes an admin's role. |
permissions | array of strings | No | A developer's or viewer's permissions. Leave it out to keep the current ones. Ignored for admins. |
Example
const member = await abusezero.updateMember("41958302746610938471", { role: "viewer", permissions: ["export"] }, "priya-viewer");Response
Returns 200 with the member object.
Errors
| Code | Status | Meaning |
|---|---|---|
PERMISSION_REQUIRED | 403 | The signed-in member isn't the owner or an admin, the change needs the owner, or it's their own access. |
OWNER_PROTECTED | 409 | The owner's access can't change. |
MEMBER_NOT_FOUND | 404 | No member with this ID is in the workspace. |
Suspension and restoration
Suspending or restoring a member requires identity verification in Workspace settings → Members & access. These actions are available only to the person in the dashboard; they have no API endpoint, SDK method, CLI command or MCP tool.
A suspended member cannot access that workspace through their connected apps. Restoring membership does not restore old app access: sign in and authorize the app again. Workspace API keys and machine clients remain independent of member suspension.
Remove a member
Removes a member from the workspace. They lose access at once, their OAuth access tokens for it stop working, and they get an email. Keys and machine clients belong to the workspace, so they keep working.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
DELETE | /v1/members/{id} | operations:management | Required |
Also available as abusezero members remove in the AbuseZero CLI, abusezero_remove_member on the AbuseZero MCP server and removeMember() in the AbuseZero Node.js SDK.
Response
Returns 200 with { "object": "deleted", "id": "41958302746610938471", "deleted": true }.
Errors
| Code | Status | Meaning |
|---|---|---|
PERMISSION_REQUIRED | 403 | The signed-in member isn't the owner or an admin, the member is an admin and the signed-in member isn't the owner, or it's their own access. |
OWNER_PROTECTED | 409 | The owner can't be removed. |
MEMBER_NOT_FOUND | 404 | No member with this ID is in the workspace. |
The invitation object
{
"object": "invitation",
"id": "73492810562018437529",
"email": "sam@example.com",
"role": "developer",
"invited_by": "Priya Shah",
"status": "pending",
"created_at": "2026-11-10T09:00:00.000Z",
"expires_at": "2026-11-17T09:00:00.000Z"
}| Field | Type | Description |
|---|---|---|
object | "invitation" | The object type. |
id | string | The invitation's ID. |
email | string | The address it was sent to. |
role | admin, developer or viewer | The role the person gets when they accept. |
invited_by | string or null | The name of the member who sent it. |
status | pending or canceled | canceled after it's canceled. |
created_at | string | When it was sent. |
expires_at | string | When it stops working, 7 days after it was sent. |
The invitation link and invite code go only to the invited address, in the invitation email. They're never returned.
List invitations
Returns the workspace's pending invitations, newest first. Members who aren't the owner or an admin see none, as in the dashboard.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
GET | /v1/invitations | operations:general | Not used |
Also available as abusezero invitations list in the AbuseZero CLI, abusezero_list_invitations on the AbuseZero MCP server and invitations() in the AbuseZero Node.js SDK.
Response
Returns 200 with a list of invitation objects.
Invite a member
Invites someone by email. They get the invitation email with a link and an invite code, valid for 7 days. Inviting an address again replaces its pending invitation.
Each pending invitation takes one of the workspace's team seats until it's accepted, declined, canceled or expires. When the workspace has no free seat as the person accepts, the invitation stays valid until there's room or it expires.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
POST | /v1/invitations | operations:management | Required |
Also available as abusezero invitations create in the AbuseZero CLI, abusezero_invite_member on the AbuseZero MCP server and inviteMember() in the AbuseZero Node.js SDK.
Body parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The person's email address. |
role | admin, developer or viewer | Yes | Their role when they accept. Only the owner invites admins. |
Example
const invitation = await abusezero.inviteMember({ email: "sam@example.com", role: "developer" }, "invite-sam");Response
Returns 201 with the invitation object.
Errors
| Code | Status | Meaning |
|---|---|---|
PERMISSION_REQUIRED | 403 | The signed-in member isn't the owner or an admin, or only the owner can invite an admin. |
MEMBER_EXISTS | 409 | This person is already a member. |
RATE_LIMITED | 429 | The signed-in member sent too many invitations recently. |
Resend an invitation
Sends a pending invitation again, as a new invitation with a new ID that replaces it. Only the member who sent it, or the owner, can resend it.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
POST | /v1/invitations/{id}/resend | operations:management | Required |
Also available as abusezero invitations resend in the AbuseZero CLI, abusezero_resend_invitation on the AbuseZero MCP server and resendInvitation() in the AbuseZero Node.js SDK.
Response
Returns 201 with the new invitation object.
Errors
| Code | Status | Meaning |
|---|---|---|
INVITATION_NOT_FOUND | 404 | The invitation isn't pending anymore. Invite the person again. |
PERMISSION_REQUIRED | 403 | Only the member who sent it, or the owner, can resend it. |
Cancel an invitation
Cancels a pending invitation, so its link and invite code stop working. Only the member who sent it, or the owner, can cancel it.
| Method | Path | Scope | Idempotency-Key |
|---|---|---|---|
POST | /v1/invitations/{id}/cancel | operations:management | Required |
Also available as abusezero invitations cancel in the AbuseZero CLI, abusezero_cancel_invitation on the AbuseZero MCP server and cancelInvitation() in the AbuseZero Node.js SDK.
Response
Returns 201 with the invitation object, with status canceled.
Errors
| Code | Status | Meaning |
|---|---|---|
INVITE_NOT_FOUND | 404 | No invitation with this ID exists in the workspace. |
INVITE_ENDED | 409 | The invitation was already accepted, declined, canceled or replaced, or it expired. |
PERMISSION_REQUIRED | 403 | Only the member who sent it, or the owner, can cancel it. |
For every other code, see REST API errors.
Related
How is this guide?
Last updated on