Members

Members are the people in your organization. Each is an owner, admin or member. Owners and admins manage members in the portal; API keys with the members:* scopes do the same, except that an API key cannot change or remove owners, or make someone an owner.

Inviting someone

curl -X POST https://api.1keyplatform.dev/v1/invitations \
  -H "Authorization: Bearer $ONEKEY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]", "role": "member"}'

1key emails the address a link that works for 7 days. Opening it adds them to your organization, creating their account if they have none. role is admin or member, and defaults to member. Needs members:write.

GET /invitations lists the pending ones; DELETE /invitations/{id} revokes one, so its link stops working.

Listing and changing members

curl https://api.1keyplatform.dev/v1/members \
  -H "Authorization: Bearer $ONEKEY_API_KEY"

{
  "data": [
    { "id": "4b0f…", "email": "[email protected]", "role": "owner", "joined_at": "2026-09-12T15:20:00Z" },
    { "id": "9c2e…", "email": "[email protected]", "role": "member", "joined_at": "2026-10-01T10:02:11Z" }
  ],
  "has_more": false
}

PATCH /members/{id} with {"role": "admin"} or {"role": "member"} changes a role; DELETE /members/{id} removes someone. Both need members:write, and both answer 403 forbidden for an owner.