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

Retrieve Parse Webhook settings

API Overview

api-overview page anchor

The SendGrid Event Webhook sends email event data as SendGrid processes it. This means you can receive data in nearly real-time, making it ideal to integrate with logging or monitoring systems.

Because the Event Webhook delivers data to your systems, it is also well-suited to backing up and storing event data within your infrastructure to meet your own data access and retention needs.

Event types

event-types page anchor

You can think about the types of events provided by the Event Webhook in two categories: deliverability events and engagement events.

  • Deliverability events such as "delivered," "bounced," and "processed" help you understand if your email is being delivered to your customers.
  • Engagement events such as "open," and "click" help you understand if customers are reading and interacting with your emails after they arrive.

Both types of events are important and should be monitored to understand the overall health of your email program. The Webhooks API allows you to configure your Event Webhook configurations.

Data storage

data-storage page anchor

Currently, data staged to be be posted through the webhooks is stored in the US.

Operation overview

operation-overview page anchor

GET/v3/user/webhooks/parse/settings

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 all of your current inbound parse settings.

Operation details

operation-details page anchor

Authentication

authentication page anchor

Headers

headers 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.

Responses

responses page anchor
200401403404500
SchemaExample
Property nameTypeRequiredDescriptionChild properties
resultarray[object]

The list of your current inbound parse settings.

Retrieve all parse settingsLink to code sample: Retrieve all parse settings
1
const client = require('@sendgrid/client');

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

3


4


5
const request = {

6
  url: `/v3/user/webhooks/parse/settings`,

7
  method: 'GET',

8
  

9
}

10


11
client.request(request)

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

13
    console.log(response.statusCode);

14
    console.log(response.body);

15
  })

16
  .catch(error => {

17
    console.error(error);

18
  });