Rate this page:

How to Create a Subuser with the API

Creating a new subuser through SendGrid's API is a multi-step process. This guide will walk you through the necessary steps to create a new subuser account using only API calls.

Establish the New Subuser (required)

With the subuser creation API call you will be able to establish the new subuser's account and profile settings. This call will create the new subuser account. However, it does not apply the sending IP for the account, nor does it establish a domain authentication entry or enable website/SMTP access for the subuser.

Call Example


Success Message

Establish subuser success message.

Failure Message

Establish subuser failure message.

Assign an IP to be Used by the New Subuser (required)

Now that you have created the new subuser account, you will need to add an IP so that it can send emails. We advise that you first find an available IP for this subuser. You can do so by using the following call:

Call Example


When defining the parameter 'list', there are a few options you can choose:

  • All - Will list all of the IPs on your account, taken or available.
  • Free - Will list all the free IPs on your account. For instance, if an IP is in use by a subuser or parent account then that IP will not be listed.
  • Taken - Will list all of the IP addresses that are assigned to your parent and subuser accounts.
  • Available - Will list all of the unassigned IP addresses for the account. If a subuser is deactivated and it is assigned an IP, that IP will show up on this list since that IP address is not technically in use.

Response Example

Assign IP response example.

After you have selected the IP that you wish to assign to your subuser account, make the API call to append the IP address.

Call Example


When defining this call's 'set' parameter, you have a few options for appending the subuser's IP:

  • None - removes all of the IPs on the associated account.
  • All - applies all of the possible IPs to the account.
  • Specify - Specify the IPs to the subuser

Success Message

Call success message.

Failure Message

Call failure message.

Assign a domain authentication for the Subuser Account (optional)

After you have created the subuser account and have appended an IP address, you are now ready to assign an existing authenticated domain to the account. If you have not yet created the required records for authenticating your chosen domain then this step should be skipped.

First, you should find out what authenticated domains you have associated with your account. This call will list your available authenticated domains:

Call Example


Response Example

Assign domain response example.

The API response above shows that email.sendgrid.com and email.example.com are both already established domain entries, and can be used by this subuser. If none are displayed then the next step in this process should be skipped.

If you have an authenticated domain entry that you wish to apply to your subuser then you will need to append the authenticated domain entry to your subuser:

Call Example


Success Message

Assign domain success message.

Failure Message

Assign domain failure message.

Authenticating the Subuser to Have Website/SMTP Access (required)

The final step in creating your new subuser requires you to activate the subuser account so that they have a website and SMTP access.

Call Example


Success Message

Authenticate subuser success message.

Failure Message

Authenticate subuser failure message.

Additional Resources

Rate this page:

Need some help?

We all do sometimes. Get help now from the Twilio SendGrid Support Team.

Running into a coding hurdle? Lean on the wisdom of the crowd by browsing the SendGrid tag on Stack Overflow or visiting Twilio's Stack Overflow Collective.

Loading Code Sample...

        Thank you for your feedback!

        Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

        Sending your feedback...
        🎉 Thank you for your feedback!
        Something went wrong. Please try again.

        Thanks for your feedback!