Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Invite teammate



API Overview

api-overview page anchor

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 makes it easy to add, remove, and manage different users. See the Teammate Permissions documentation for more information about manaing user permissions.

(information)

Info

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(link takes you to an external 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.


POST/v3/teammates

Base url: https://api.sendgrid.com

This endpoint allows you to invite a Teammate to your account via email.

You can set a Teammate's initial permissions using the scopes array in the request body. Teammate's will receive a minimum set of scopes from Twilio SendGrid that are necessary for the Teammate to function.

Note: A teammate invite will expire after 7 days, but you may resend the invitation at any time to reset the expiration date.


Authentication

authentication page anchor
Property nameTypeRequiredDescription
Authorizationstringrequired
Default: Bearer <<YOUR_API_KEY_HERE>>

on-behalf-ofstringOptional

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.

SchemaExample
Property nameTypeRequiredDescriptionChild properties
emailstringrequired

New teammate's email

Pattern: ^.*@.*\..*Min length: 5Max length: 255

scopesarray[string]required

Set to specify list of scopes that teammate should have. Should be empty if teammate is an admin.


is_adminbooleanrequired

Set to true if teammate should be an admin user

Default: false
201400
SchemaExample
Property nameTypeRequiredDescriptionChild properties
tokenstring

Token to identify invite


emailstring

Teammate's email address


scopesarray

Initial set of permissions to give to teammate if they accept the invite


is_adminboolean

Set to true if teammate should have admin privileges

Invite teammate

invite-teammate page anchor
Node.js
Python
C#
Java
Go
PHP
Ruby
curl

_26
const client = require('@sendgrid/client');
_26
client.setApiKey(process.env.SENDGRID_API_KEY);
_26
_26
const data = {
_26
"email": "teammate1@example.com",
_26
"scopes": [
_26
"user.profile.read",
_26
"user.profile.update"
_26
],
_26
"is_admin": false
_26
};
_26
_26
const request = {
_26
url: `/v3/teammates`,
_26
method: 'POST',
_26
body: data
_26
}
_26
_26
client.request(request)
_26
.then(([response, body]) => {
_26
console.log(response.statusCode);
_26
console.log(response.body);
_26
})
_26
.catch(error => {
_26
console.error(error);
_26
});


Rate this page: