client.members
Çdo metodë në këtë hapësirë emrash: nënshkrimi, parametrat, çfarë kthen dhe një shembull.
Metodat
People who share the workspace, their role and the addresses they may use, and the invitations still waiting.
members.list
List everybody with access to the workspace
list(limit: nil, cursor: nil, api_key: nil) -> OpenEmail::PageReturns one page of the workspace's members, the owner first and the rest by email. list_all collects every page and iterate walks them lazily. Each row carries two axes that a client must not merge: role and permissions say what the person may do, and addresses and domains say what they may do it to, each with its own access. A whole domain reaches every address on it, including ones made later. A send needs both axes, so emails:send with nothing granted sends from nothing.
The one exception is addresses:all. When permissions holds it, the person reaches every address on every domain of the workspace, including ones added later, and sends as any of them when permissions also holds emails:send. addresses and domains still list only the grants made to them directly, which they may have kept from before or been given since, or none at all. Read reach from permissions first, and from those two arrays only when it lacks addresses:all.
The list is a union of people with a membership row and people who only hold address or domain grants and no membership row. The second group comes back with implied: true, role[:id] nil and createdAt nil, and their role is inferred from their grants: Member if any grant has access: "member", Viewer otherwise. Until someone calls update for them, widening their addresses silently widens what they may do.
The workspace owner is the FIRST row, marked isOwner: true, so an unshared workspace returns one member rather than an empty page. They hold every permission by definition, and add, update and remove refuse them with member_is_owner. Exclude isOwner when counting seats.
Parametrat
limitIntegerPage size, from 1 to 100. The server defaults to 25.
cursorStringThe
next_cursorof the previous page. Leave it out for the first page.api_keyStringOverrides the client API key for this call only.
Kthen
An OpenEmail::Page of Hashes, with items, has_more? and next_cursor. Each item has userId, email, name, image, isOwner, role, implied, permissions, addresses, domains and createdAt.
Shembull
members = client.members.list_all unreviewed = members.select { |member| member[:implied] } p unreviewed.map { |member| [member[:email], member[:role][:name], member[:addresses].size] }Shënime
Every other method here takes
user_id, the account id, not the email address.access: "viewer"on an address blocks sending from it even when the role holdsemails:send, unless the role also holdsaddresses:all. Otherwise the two axes are ANDed, never added.The cursor is opaque and holds where the last row sat in this order, so a row deleted or edited between pages never breaks the walk: the next page starts at the first row that sorts after it. A cursor this list did not hand out is a 400
invalid_cursor.
E disponueshme edhe në
- API
GET /members- TypeScript
members.list()- Python
members.list()- CLI
openemail members list
members.list_all
Collect every member into one array
list_all(limit: nil, cursor: nil, api_key: nil) -> Array<Hash>Walks every page of list and returns all members in one Array, the owner first and the rest by email. One request per page.
Parametrat
limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
Kthen
An Array of Hashes holding every member, each with the fields list returns.
Shembull
all = client.members.list_all(limit: 100) puts all.sizeShënime
If any page fails, the error is raised and the members already fetched are discarded.
E disponueshme edhe në
- API
GET /members- TypeScript
members.listAll()- Python
members.list_all()
members.iterate
Stream the members one at a time
iterate(limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>Returns an Enumerator that yields members individually, the owner first and the rest by email, and requests the next page only once the current one is drained. Nothing is fetched until you consume it, and breaking out of the loop stops the requests. Given a block, it yields each member to the block instead.
Parametrat
limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
Kthen
An Enumerator of Hashes, one member per step (or yields each one to a block).
Shembull
client.members.iterate do |item| p itemendShënime
Pages are fetched only as they are needed, so an abandoned loop costs only the pages you consumed.
E disponueshme edhe në
- API
GET /members- TypeScript
members.iterate()- Python
members.iterate()
members.get
Read one member by account id
get(user_id, api_key: nil) -> HashReturns a single member with their role, resolved permissions and address grants. The lookup runs over the same union as list, so a legacy grant holder with no membership row is found here too, with implied: true.
The path takes the account id from list, not an email. An email can change on the account, and a stale one would point at the wrong person. The owner is not a member, so their account id answers 404 like any unknown one.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash with role (a Hash of id, name and builtin), implied, the resolved permissions, and addresses, each holding addressId, address and access.
Shembull
member = client.members.get("q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E") puts member[:role][:name], member[:implied]p member[:addresses].map { |grant| [grant[:address], grant[:access]] }Shënime
A missing member is 404
resource_not_found.For an implied member,
permissionsare the Member or Viewer template permissions, not a stored role thatroles.getcould read.
E disponueshme edhe në
- API
GET /members/{userId}- TypeScript
members.get()- Python
members.get()- CLI
openemail members get
members.add
Invite somebody to the workspace with a role
add(body = nil, api_key: nil, **fields) -> HashSends an invitation to join the workspace. Whether or not the address already has an OpenEmail account, the answer is an invitation rather than a member: nobody is put into a workspace without accepting, and this method is held to the same rule as the app.
The invitation carries the role, the addresses and the whole domains you name, and grants exactly those the moment it is accepted. Nothing is granted before that. Calling it again for the same address within ten minutes is refused with 409 invitation_too_soon; after that it refreshes the one outstanding invitation rather than sending a second.
Somebody already in the workspace is refused with 422 member_is_owner. Change what an existing member may do with update, grant_address and revoke_address, which only work on people already in.
Role and grants are separate axes. access applies to every id in addressIds and domainIds, and it never widens the role: access: "member" under a role without emails:send still cannot send. A role holding addresses:all reaches every address without any ids, and no key or access token can invite with one, because none of them holds that console-only permission.
Parametrat
emailStringE detyrueshmeWho to invite. Trimmed and lowercased. It does not need to have an account yet.
roleIdStringE detyrueshmeRole id from
roles.list. The owner role is refused with 409role_immutable, and a role holding more than the key itself holds is refused with 403insufficient_authority. That covers every role with a console-only permission in it, such asaddresses:all.addressIdsArray<String>Up to 64 address ids on this workspace the invitation carries, all at
access.domainIdsArray<String>Up to 64 domain ids on this workspace the invitation carries, all at
access. A whole domain covers every address on it, including ones made later.accessStringmemberreads and sends as the granted addresses,vieweronly reads them. Defaults tomember.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the invitation, answered with a 202, holding the invitation id, what it carries, when it expires, and delivered, which is false when the email did not leave the mail server.
Shembull
invitation = client.members.add( email: "[email protected]", roleId: "role_8b1f4c2e9a7d3b60e5f1a2c4", domainIds: ["93542ff8-2baa-4f2f-841d-5ceaa074ab0d"], access: "member") puts invitation[:id], invitation[:delivered], invitation[:expiresAt]Shënime
An unknown
roleIdis 404role_not_foundwithparamset toroleId. An address or domain id that is not on this workspace is 422member_not_foundwithparamset toaddressIdordomainId.The workspace owner, and anybody already in the workspace, is refused with 422
member_is_owner.delivered: falsemeans the invitation exists but the email did not go out. It can be sent again from the app once the ten minute cooldown has passed.Not retried automatically. Re-posting the same body inside ten minutes is 409 rather than a duplicate.
E disponueshme edhe në
- API
POST /members- TypeScript
members.add()- Python
members.add()- CLI
openemail members add
members.update
Change the role a member holds
update(user_id, patch = nil, api_key: nil, **fields) -> HashMoves a member to a different role and changes nothing else, for somebody ALREADY in the workspace. Their address and domain grants are untouched, and grants cannot be patched here at all: grant_address and revoke_address change one grant at a time.
This is also how a legacy grant holder stops being implied. They have address or domain grants and no membership row, this writes one, and from then on implied is false and their permissions come from a role someone chose rather than from what their access implied.
Nobody joins through update. An account that is not in the workspace is 422 member_not_found: invite them with add and they are in once they accept. The owner role cannot be handed out, which is 409 role_immutable, and the workspace owner cannot be given a role, which is 422 member_is_owner.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.roleIdStringE detyrueshmeId of the role to move them to.
api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the member with the new role and permissions, and implied set to false.
Shembull
member = client.members.update("q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E", roleId: "role_2c7e9a1f4b8d3e60c5a7f1b9") puts member[:role][:name], member[:implied]Shënime
The account has to be in the workspace already, by membership row or by a grant. Anybody else is 422
member_not_found; useaddto invite them.An unknown
roleIdis 404role_not_found, and a user id with no OpenEmail account behind it is 404user_not_found.A role holding more than the key itself holds is 403
insufficient_authority. No key or access token holds a console-only permission, so a role withaddresses:all, billing orworkspace:managein it is handed out only in the app. That includes the seeded Admin, which holds billing.Retried automatically on network failure, since it names the role it wants and a replay lands on the same row.
E disponueshme edhe në
- API
PATCH /members/{userId}- TypeScript
members.update()- Python
members.update()- CLI
openemail members update
members.remove
Remove a member and every address grant they hold
remove(user_id, api_key: nil) -> HashTakes somebody out of the workspace entirely: the membership row and every address grant they hold on it. Removing only the row would drop them from the list while they kept reading the mail, so both go together.
It does not 404 for somebody who is not a member. The people this most needs to reach are legacy grant holders with no membership row, so there is no existence check, and addressesRevoked reports what actually happened. Zero is the honest answer for a no-op.
Their account, their sent mail and anything they wrote are untouched. Only their access to this workspace ends.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash with object set to member, the userId, deleted set to true and addressesRevoked.
Shembull
removed = client.members.remove("q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E") puts removed[:deleted], removed[:addressesRevoked]Shënime
Idempotent on the server, but the SDK does not retry it automatically, so repeat it yourself after a network failure.
The workspace owner is refused with 422
member_is_owner, because their access never came from a membership.
E disponueshme edhe në
- API
DELETE /members/{userId}- TypeScript
members.remove()- Python
members.remove()- CLI
openemail members remove
members.grant_address
Grant a member one address or change their access to it
grant_address(user_id, body = nil, api_key: nil, **fields) -> HashGives one person one address on this workspace, or changes the access they already have to it. It is an upsert: there is one grant per person and address, so posting again with a different access turns a viewer into a member rather than adding a second grant.
This is the address axis and it cannot widen the role. access: "member" lets somebody send as the address only if their role also holds emails:send, and otherwise it lets them read.
Granting an address to an account with no membership row makes them appear in list as an implied member whose role is inferred from their grants, so call update as well if the role should be a decision. The whole member comes back, which lets a client redraw the row without another read.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.addressIdStringE detyrueshmeId of an address on this workspace.
accessStringmemberreads and sends as the address,vieweronly reads it. Defaults tomember.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the member with the grant applied, including the full addresses list.
Shembull
member = client.members.grant_address( "q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E", addressId: "4f0c1b6e-2d7a-4a9e-8c35-91b2e7d4f6a0", access: "viewer") p member[:addresses]Shënime
An address id that is not on this workspace is 422 with code
member_not_foundandparamset toaddressId.The workspace owner is refused with 422
member_is_owner, since they already reach every address. A user id with no OpenEmail account behind it is 404user_not_found.Gated on
members:writerather than on owning the address, so an admin who owns nothing can still manage grants.Retried automatically on network failure, since replaying the same grant lands on the same row.
E disponueshme edhe në
members.revoke_address
Take one address back from a member
revoke_address(user_id, address_id, api_key: nil) -> HashRemoves one address grant and leaves the person in the workspace with their role and their other addresses. This is the narrow revocation to use when somebody changes team.
An address id that is not on this workspace is refused with 422 member_not_found rather than ignored, so a typo cannot report a revocation that never happened. An address that is on the workspace but was never granted to this person is a silent no-op, and the member comes back unchanged.
The member is returned rather than a tombstone, because the useful answer is what they can still reach.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.address_idStringE detyrueshmeId of an address on this workspace.
api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the member with the remaining addresses.
Shembull
member = client.members.revoke_address("q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E", "4f0c1b6e-2d7a-4a9e-8c35-91b2e7d4f6a0") p member[:addresses].map { |grant| grant[:address] }Shënime
Revoking the last grant of an implied member removes them from the workspace entirely. The call still succeeds and returns the member as they stood, without that address.
Somebody who is not a member of this workspace is a 404.
Not retried automatically by the SDK.
E disponueshme edhe në
members.grant_domain
Grant a member a whole domain or change their access to it
grant_domain(user_id, body = nil, api_key: nil, **fields) -> HashGives one person every address on one domain of this workspace, including addresses added after the grant, or changes the access they already have to it. It is an upsert: there is one grant per person and domain, so calling it again with a different access turns a viewer into a member rather than adding a second grant.
This is the address axis and it cannot widen the role. access: "member" lets somebody send from the domain only if their role also holds emails:send, and otherwise it lets them read.
The person has to be in the workspace already, so invite them with add first. The whole member comes back, with the grant in domains.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.domainIdStringE detyrueshmeId of a domain on this workspace, as
domains.listreturns it.accessStringmemberreads and sends from the domain,vieweronly reads it. Defaults tomember.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the member with the grant applied, including the full domains list.
Shembull
member = client.members.grant_domain( "q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E", domainId: "7d2a9c41-5b3e-4f8a-9c06-1e2b3c4d5e6f", access: "viewer") p member[:domains]Shënime
A domain id that is not on this workspace is 422 with code
member_not_foundandparamset todomainId. Somebody who is not in the workspace yet is refused the same way withparamset touserId.The workspace owner is refused with 422
member_is_owner, since they already reach every domain. A user id with no OpenEmail account behind it is 404user_not_found.A workspace whose plan has no team access is refused with 403
plan_required. A key or an access token limited to particular addresses or domains is refused with 422capability_unsupported, and an access token acting for a member can only give a domain that member reaches, or it is refused with 403insufficient_authority.An OAuth access token needs a verification code for this call, and is refused with 403
step_up_requireduntil the app has verified one in the last 60 minutes.step_up_required?on the error says so. An API key is never asked for a code.Retried automatically on network failure, since replaying the same grant lands on the same row.
E disponueshme edhe në
members.revoke_domain
Take a whole domain back from a member
revoke_domain(user_id, domain_id, api_key: nil) -> HashRemoves one domain grant and leaves the person in the workspace with their role and their other grants. Addresses on that domain that were granted to them one by one stay granted.
A domain id that is not on this workspace is refused with 422 member_not_found rather than ignored, so a typo cannot report a revocation that never happened. A domain that is on the workspace but was never granted to this person is a silent no-op, and the member comes back unchanged.
The member is returned rather than a tombstone, because the useful answer is what they can still reach.
Parametrat
user_idStringE detyrueshmeThe account id from
list, not the email address.domain_idStringE detyrueshmeId of a domain on this workspace.
api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the member with the remaining domains.
Shembull
member = client.members.revoke_domain("q7Vd3kX9mT2pLw8RzN4bYc6HfJ1sGa5E", "7d2a9c41-5b3e-4f8a-9c06-1e2b3c4d5e6f") p member[:domains].map { |grant| grant[:domain] }Shënime
Somebody who is not a member of this workspace is a 404.
A key or an access token limited to particular addresses or domains is refused with 422
capability_unsupported.An OAuth access token needs a verification code for this call, and is refused with 403
step_up_requireduntil the app has verified one in the last 60 minutes.step_up_required?on the error says so. An API key is never asked for a code.Not retried automatically by the SDK.
E disponueshme edhe në
members.list_invitations
List the invitations nobody has accepted yet
list_invitations(limit: nil, cursor: nil, api_key: nil) -> OpenEmail::PageReturns one page of the invitations to this workspace that are still waiting, by email: the role and the addresses and whole domains each one grants once accepted, when it expires, and whether the last email reached them. list_all_invitations collects every page and iterate_invitations walks them lazily.
A waiting invitation grants nothing. It becomes access only at the moment somebody accepts it, which is why it is listed apart from list. An expired one stays on the list with expired: true until it is sent again or withdrawn.
Parametrat
limitIntegerPage size, from 1 to 100. The server defaults to 25.
cursorStringThe
next_cursorof the previous page. Leave it out for the first page.api_keyStringOverrides the client API key for this call only.
Kthen
An OpenEmail::Page of Hashes, with items, has_more? and next_cursor. Each item has id, email, role, addresses, domains, expiresAt, expired, lastSentAt, delivered, deliveryError and createdAt.
Shembull
page = client.members.list_invitations stale = page.items.select { |invitation| invitation[:expired] } puts stale.map { |invitation| invitation[:email] }Shënime
deliveredis nil when no send outcome was recorded, false when the email did not leave the mail server, with the reason indeliveryError.A key limited to particular addresses or domains lists only the invitations that grant nothing outside them.
E disponueshme edhe në
members.list_all_invitations
Collect every waiting invitation into one array
list_all_invitations(limit: nil, cursor: nil, api_key: nil) -> Array<Hash>Walks every page of list_invitations and returns every waiting invitation in one Array, by email. One request per page, with the same filters on each.
Parametrat
limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
Kthen
An Array of Hashes holding every waiting invitation, each with the fields list_invitations returns.
Shembull
all = client.members.list_all_invitations p all.map { |invitation| [invitation[:email], invitation[:role][:name]] }Shënime
If any page fails, the error is raised and the rows already fetched are discarded.
E disponueshme edhe në
members.iterate_invitations
Stream the waiting invitations one at a time
iterate_invitations(limit: nil, cursor: nil, api_key: nil, &block) -> Enumerator<Hash>Returns an Enumerator that yields one invitation at a time, by email, and requests the next page only once the current one is drained. Nothing is fetched until you consume it, and breaking out of the loop stops the requests. Given a block, it yields each invitation to the block instead.
Parametrat
limitIntegerPage size for each request, from 1 to 100. The server defaults to 25.
cursorStringStarts the walk after this cursor instead of the first page.
api_keyStringOverrides the client API key for every page of this walk.
Kthen
An Enumerator of Hashes, one invitation per step (or yields each one to a block).
Shembull
client.members.iterate_invitations do |invitation| puts "#{invitation[:email]} #{invitation[:deliveryError]}" if invitation[:delivered] == falseendShënime
Pages are fetched only as they are needed, so an abandoned loop costs only the pages you consumed.
E disponueshme edhe në
members.revoke_invitation
Withdraw an invitation
revoke_invitation(invitation_id, api_key: nil) -> HashWithdraws an invitation nobody has accepted. Its link stops working at once and nothing it would have granted is granted. It is Withdraw on the members screen. Inviting the same address later with add sends a new one.
Parametrat
invitation_idStringE detyrueshmeThe invitation id from
list_invitations.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash with object set to invitation, the id, the email, and revoked set to true.
Shembull
withdrawn = client.members.revoke_invitation("winv_6bb640f5b99e47deb758f1f5") puts withdrawn[:email], withdrawn[:revoked]Shënime
An invitation that was accepted first answers 409
invitation_accepted: remove the member instead. One that is unknown or already withdrawn answers 404.A key limited to particular addresses or domains can withdraw only an invitation that grants nothing outside them.
E disponueshme edhe në
members.resend_invitation
Send an invitation again
resend_invitation(invitation_id, api_key: nil) -> HashSends a waiting invitation again: a new link, fourteen more days, and the old link retired, so only the newest email works. It is Send again on the members screen, and it renews an expired invitation too.
Parametrat
invitation_idStringE detyrueshmeThe invitation id from
list_invitations.api_keyStringOverrides the client API key for this call only.
Kthen
A Hash for the invitation with the new expiresAt and lastSentAt, and delivered for this send.
Shembull
invitation = client.members.resend_invitation("winv_6bb640f5b99e47deb758f1f5") puts invitation[:expiresAt], invitation[:delivered]Shënime
The same address cannot be sent to twice within ten minutes: that is 409
invitation_too_soon. The daily limit on invitations is 409invitation_limit_reached.The invitation's role cannot hold more than the key does, the rule
addapplies too: a role with a permission the key or access token lacks, any console-only one such asaddresses:allincluded, is 403insufficient_authority. An access token acting for a member is also refused with it when the invitation carries addresses or domains that member does not reach.The SDK does not retry it, because each call sends an email.