Skip to contentSkip to navigationSkip to topbar
Twilio SendGrid Docs
On this page

Retrieve an existing API Key

API Overview

api-overview page anchor

Your application, mail client, or website can all use API (Application Programming Interface) keys to authenticate access to SendGrid services. You can revoke an API key at any time without having to change your username and password, and an API key can be scoped to perform a limited number of actions.

There are 3 different types of API keys:

  • Full Access
    Allows the API key to access GET, PATCH, PUT, DELETE and POST endpoints for all parts of your account, excluding billing and Email Address Validation.
  • Restricted Access
    Customizes levels of access for all parts of your account, excluding billing and Email Address Validation.
  • Billing Access
    Allows the API key to access billing endpoints for the account.

You must create your first API key using the Twilio SendGrid App(link takes you to an external page). Once you have a key with permissions to manage other keys, you can use the endpoints documented as part of this API.

(warning)

Warning

Twilio SendGrid API keys are 69 characters long. We are unable to make exceptions for third-party infrastructure that is unable to support a key of 69 characters.

Operation overview

operation-overview page anchor

GET/v3/api_keys/{api_key_id}

Base url: https://api.sendgrid.com (for global users and subusers)

Base url: https://api.eu.sendgrid.com (for EU regional subusers)

This endpoint allows you to retrieve a single API key using an api_key_id.

The endpoint will return a key's name, ID, and scopes. If the API Key ID does not, exist a 404 status will be returned.

See the API Key Permissions List for all available scopes. An API key's scopes can be updated after creation using the "Update API keys" endpoint.

Operation details

operation-details page anchor

Authentication

authentication page anchor

Headers

headers page anchor
Property nameTypeRequiredDescription
authorizationstring
required
Default: Bearer <<YOUR_API_KEY_HERE>>
onBehalfOfstring

Optional

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.

Path parameters

path-parameters page anchor
Property nameTypeRequiredDescription
apiKeyIdstring
required

Responses

responses page anchor
200400401403404500
SchemaExample
Property nameTypeRequiredDescriptionChild properties
resultarray[API Key Name, ID, and Scopes]

Optional

Retrieve an existing API KeyLink to code sample: Retrieve an existing API Key
1
const client = require("@sendgrid/client");

2
client.setApiKey(process.env.SENDGRID_API_KEY);

3


4
const api_key_id = "ZGkrHSypTsudrGkmdpJJ";

5


6
const request = {

7
  url: `/v3/api_keys/${api_key_id}`,

8
  method: "GET",

9
};

10


11
client

12
  .request(request)

13
  .then(([response, body]) => {

14
    console.log(response.statusCode);

15
    console.log(response.body);

16
  })

17
  .catch((error) => {

18
    console.error(error);

19
  });