How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SendGrid Subusers API

Twilio SendGrid Subusers API

SendGrid Subusers API is one of 63 APIs that SendGrid publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Subusers. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 6 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.sendgrid.com, https://api.eu.sendgrid.com.

9 operations 6 paths 13 schemas 1 DELETE3 GET2 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.sendgrid.com
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

SendGrid Subusers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Twilio SendGrid requires you to authenticate with its APIs using an API key. The API key must be sent as a bearer token in the Authorization header.

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 3 GET, 2 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Subusers 9

Twilio SendGrid Subusers API

GET
/v3/subusers
List all Subusers
ListSubuser 5 params → 200401
POST
/v3/subusers
Create Subuser
CreateSubuser body → 200400401403500
PATCH
/v3/subusers/{subuser_name}
Enable/disable a subuser
UpdateSubuser 1 param body → 204400401500
DELETE
/v3/subusers/{subuser_name}
Delete a subuser
DeleteSubuser 1 param → 204401
GET
/v3/subusers/{subuser_name}/credits
Get the Credits for a Subuser
GetSubuserCredit 1 param → 200400
PUT
/v3/subusers/{subuser_name}/credits
Update the Credits for a Subuser
UpdateSubuserCredit 1 param body → 200400
PATCH
/v3/subusers/{subuser_name}/credits/remaining
Update the remaining credits for a Subuser
UpdateSubuserRemainingCredit 1 param body → 200400
PUT
/v3/subusers/{subuser_name}/ips
Update IPs assigned to a subuser
UpdateSubuserIp 1 param body → 200401
GET
/v3/subusers/reputations
Retrieve Subuser Reputations
ListReputation 1 param → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SubuserPost (5 properties), Subuser (5 properties), SubuserCredits (5 properties), SubuserCreditsRequest (3 properties). Each schema is shown below with its type and property counts.

SubuserPost
object
5 properties 3 required
Type
string
Region1
string
SubuserCreditsRequest
object
3 properties 1 required
Type1
string
Region3
string
ResetFrequency
string
Subuser
object
5 properties 4 required
ErrorResponse
object
2 properties
Region2
string
Region
string
ResetFrequency1
string
SubuserCredits
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sendgrid-subusers-api-openapi.yml Raw ↑

Other APIs SendGrid publishes across the network.

SendGrid Account API
SendGrid Account State API
SendGrid Alerts API
SendGrid API Keys API
SendGrid Blocks API
SendGrid Bounces API
SendGrid Bulk Email Address Validation API
SendGrid Campaigns API API
SendGrid Categories API
SendGrid Contacts API
SendGrid Custom Fields API
SendGrid Designs API
Where this information came from

This is an independent, third-party profile of SendGrid Subusers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.