I have the following file that handles my sendgrid set up.

import sgMail from '@sendgrid/mail';

const sendGridApiKey = process.env.SENDGRID_API_KEY;

if (!sendGridApiKey) {
  throw new Error('The sendgrid api key has not been set in the environment variables');
}

sgMail.setApiKey(sendGridApiKey);

export { sgMail };

After setting my api key I need to be able to do som

Issue Summary

See the private variables here. The TrackingSettings object can be used as an example of how to do this.

Hi, is there a minimal example of using the Single Sends function through Python3? I'm having some trouble with authentication issues to do with verified Sender IDs and suppression groups, and it would really help to see some skeleton code for a working example.

SendGrid has added an API to download information from the Email Activity feed. There are four new endpoints:

• GET /messages
• GET /messages/{msg_id}
• POST /messages/download/

We were previously using gometalinter, but it is now deprecated and golangci-lint is the recommended replacement.

Issue Summary

Right now we are migrating from Mailgun to Sendgrid, due to their generally bad IP reputation on Outlook 365 and other mail service providers. We nearly finished the migration, but right now we are experiencing a showstopper for us:

We have a subdomain for each ouf our customers (customer1.mycompany.com., customernext123.mycompany.com,... and so on) and we also want everyt

Issue Summary

The latest sendgrid api does not support Java 9 modules. Not only is there no module-info.java your api uses split packages which disqualifies it from use in the java 9 Module system.

You get this error when you try to use it...

Module 'yourmodule' reads package 'com.sendgrid' from both 'sendgrid.java' and 'java.http.client'

Steps to Reproduce

Try to use sen

I think we should invest in some automation that keeps the dependencies safe.

Right now we can use Dependabot to keep top level dependencies up-to-date but not the nested ones for the templates themselves. My suggestion is the following:

1. Add every dependency that exists in any template as a devDependency for the root package.json
2. Create the same automation that we use in github.com