Twilio SendGrid's Teammates feature allows multiple users, or "Teammates," to work from a single SendGrid account.
Teammates enables groups of users with different roles and responsibilities to share one account, where each of these users has access to varying SendGrid features depending on their needs. By only giving your individual team members access to the features that they need to do their jobs, you can limit access to sensitive areas of your account. Teammates allows you to add, remove, and manage different users. See the Teammate Permissions documentation for more information about managing user permissions.
Free and Essentials plans allow for adding one Teammate per account and do not offer Single Sign-On (SSO), while Pro and higher plans allow for up to 1,000 Teammates and include SSO and other features. Learn more about the different Email API Plans on our pricing page.
You can think of Subusers like subaccounts. Each Subuser account is its own email ecosystem with isolated contacts, templates, suppressions, and data. Subusers feed off their parent account email credits, and all billing rolls up to the parent account. Teammates may have access to a parent account, a group of Subusers, or a single Subuser account only.
This endpoint allows you to update a teammate’s permissions.
To turn a teammate into an admin, the request body should contain an is_admin set to true. Otherwise, set is_admin to false and pass in all the scopes that a teammate should have.
Only the parent user or other admin teammates can update another teammate’s permissions.
Admin users can only update permissions.
Bearer <<YOUR_API_KEY_HERE>>The on-behalf-of header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>). See On Behalf Of for more information.
The username of the teammate that you want to retrieve.
application/jsonProvide list of scopes that should be given to teammate. If specifying list of scopes, is_admin should be set to False.
Set to True if this teammate should be promoted to an admin user. If True, scopes should be an empty array.
Teammate's username
Teammate's first name
Teammate's last name
Teammate's email address
Scopes given to teammate
Indicate the type of user: owner user, teammate admin user, or normal teammate
adminownerteammateSet to true if teammate has admin priveleges
(optional) Teammate's phone number
(optional) Teammate's website
(optional) Teammate's address
(optional) Teammate's address
(optional) Teammate's city
(optional) Teammate's state
(optional) Teammate's zip
(optional) Teammate's country
1const client = require("@sendgrid/client");2client.setApiKey(process.env.SENDGRID_API_KEY);34const username = "ZGkrHSypTsudrGkmdpJJ";5const data = {6scopes: ["user.profile.read", "user.profile.edit"],7is_admin: false,8};910const request = {11url: `/v3/teammates/${username}`,12method: "PATCH",13body: data,14};1516client17.request(request)18.then(([response, body]) => {19console.log(response.statusCode);20console.log(response.body);21})22.catch((error) => {23console.error(error);24});