Api to sg

THIS PACKAGE HAS MOVEDPlease see the latest official package here, thank you!NEW: Subscribe to email notifications for releases and breaking changes.This library allows you to quickly and easily use the SendGrid Web API v3 via Node.js.Version 3.X.X+ of this library provides full support for all SendGrid Web API v3 endpoints, including the new v3 /mail/send.This library represents the beginning of a new path for SendGrid. We want this library to be community driven and SendGrid led. We need your help to realize this goal. To help make sure we are building the right things in the right order, we ask that you create issues and pull requests or simply upvote or comment on existing issues or pull requests.Please browse the rest of this README for further detail.We appreciate your continued support, thank you!Table of ContentsInstallationQuick StartUsageUse CasesAnnouncementsRoadmapHow to ContributeTroubleshootingAboutInstallationPrerequisitesNode.js version 4, 6 or 7The SendGrid service, starting at the free levelSetup Environment VariablesUpdate the development environment with your SENDGRID_API_KEY, for example:echo "export SENDGRID_API_KEY='YOUR_API_KEY'" > sendgrid.envecho "sendgrid.env" >> .gitignoresource ./sendgrid.envInstall PackageThe following recommended installation requires npm. If you are unfamiliar with npm, see the npm docs. Npm comes installed with Node.js since node version 0.8.x therefore you likely already have it.npm install --save sendgridDependenciesNodejs-HTTP-ClientQuick StartHello EmailThe following is the minimum needed code to send an email with the /mail/send Helper (here is a full example):With Mail Helper Classvar helper = require('sendgrid').mail;var fromEmail = new helper.Email('test@example.com');var toEmail = new helper.Email('test@example.com');var subject = 'Sending with SendGrid is Fun';var content = new helper.Content('text/plain', 'and easy to do anywhere, even with Node.js');var mail = new helper.Mail(fromEmail, subject, toEmail, content);var sg = require('sendgrid')(process.env.SENDGRID_API_KEY);var request = sg.emptyRequest({ method: 'POST', path: '/v3/mail/send', body: mail.toJSON()});sg.API(request, function (error, response) { if (error) { console.log('Error response received'); } console.log(response.statusCode); console.log(response.body); console.log(response.headers);});The Mail constructor creates a personalization object for you. Here is an example of how to add to it.Without Mail Helper ClassThe following is the minimum needed code to send an email without the /mail/send Helper (here is a full example):var sg = require('sendgrid')(process.env.SENDGRID_API_KEY);var request = sg.emptyRequest({ method: 'POST', path: '/v3/mail/send', body: { personalizations: [ { to: [ { email: 'test@example.com'

} ], subject: 'Sending with SendGrid is Fun' } ], from: { email: 'test@example.com' }, content: [ { type: 'text/plain', value: 'and easy to do anywhere, even with Node.js' } ] }});sg.API(request) .then(function (response) { console.log(response.statusCode); console.log(response.body); console.log(response.headers); }) .catch(function (error) { console.log(error.response.statusCode); });sg.API(request, function (error, response) { if (error) { console.log('Error response received'); } console.log(response.statusCode); console.log(response.body); console.log(response.headers);});General v3 Web API Usagevar sg = require('sendgrid')(process.env.SENDGRID_API_KEY);var request = sg.emptyRequest({ method: 'GET', path: '/v3/api_keys'});sg.API(request) .then(function (response) { console.log(response.statusCode); console.log(response.body); console.log(response.headers); }) .catch(function (error) { console.log(error.response.statusCode); });sg.API(request, function (error, response) { if (error) { console.log('Error response received'); } console.log(response.statusCode); console.log(response.body); console.log(response.headers);});UsageSendGrid DocsLibrary Usage DocsExample CodeHow-to: Migration from v2 to v3v3 Web API Mail Send HelperUse CasesExamples of common API use cases, such as how to send an email with a transactional template.AnnouncementsPlease see our announcement regarding breaking changes. Your support is appreciated!All updates to this library are documented in our CHANGELOG and releases. You may also subscribe to email release notifications for releases and breaking changes.RoadmapIf you are interested in the future direction of this project, please take a look at our open issues and pull requests. We would love to hear your feedback.How to ContributeWe encourage contribution to our libraries (you might even score some nifty swag), please see our CONTRIBUTING guide for details.Feature RequestBug ReportsImprovements to the CodebaseTroubleshootingPlease see our troubleshooting guide for common library issues.Aboutsendgrid-nodejs is guided and supported by the SendGrid Developer Experience Team.sendgrid-nodejs is maintained and funded by SendGrid, Inc. The names and logos for sendgrid-nodejs are trademarks of SendGrid, Inc.

1.However, the GrowBig and GoGeek plan users can access all three levels of SuperCacher. SiteGround claims that a website using all three levels of SuperCacher can handle 100x more hits than a regular site without a caching mechanism.If you haven’t a SiteGround user yet, I recommend you to pick either GrowBig or GoGeek plan.Now, let’s discuss the best SuperCacher settings for your site.SG Optimizer SuperCacher SettingsPlease note that the SuperCacher Level 1, i.e., NGINX Direct Delivery is available on all SiteGround WordPress hosting plans.With NGINX Direct Delivery SiteGround serves most of the static resources, including images, JS, and CSS on your website directly through NGINX to achieve the fastest page speed possible. You can enable this option by visiting your SiteGround account and navigating to the Site Tools > Speed > Caching.The Dynamic Caching and Memcached options are available in the SiteGround account as well as under SG Optimizer SuperCacher Settings.The dynamic caching is a full-page caching solution powered by NGINX that stores your content in the server’s memory for faster access.Memcached is an advanced object caching solution that stores frequently executed queries to the databases and reuses them to achieve better performance.I recommend you to get the benefit of both caching solutions to improve your page loading speed.2. Environment OptimizationThe Server Environment Optimization tab helps you configure various options to ensure the best performance.➤ Enable HTTPSThis option helps you enable a proper HTTPS configuration and forces a secure connection to the site.SG Optimizer Enable HTTPSYou can also fix the insecure content errors by rewriting the insecure requests for resources.➤ WordPress Heartbeat Optimization Enabling this option allows the SiteGround SG Optimizer to control WordPress Heartbeat API.The WordPress Heartbeat API checks for the page edits every 15 seconds or scheduled tasks after every 60 seconds. Such activities generate high CPU usage when you are logged into the WordPress admin panel or have multiple tabs open for a longer period.The SG Optimizer WordPress Heartbeat Optimization option allows you to run these checks less frequently or disable them.SG Optimizer WordPress Heartbeat Optimization➤ DNS Pre-fetch for External DomainsDNS pre-fetching for external domains saves DNS lookup time for resources loaded from these domains.SG Optimizer DNS Pre-fetch for External DomainsIf you embed tweets, YouTube videos, Vimeo videos, Facebook Like Box, Amazon affiliate links, or any content that requires external resources to be fetched to render a web page, add these domains under the DNS pre-fetch option

Are processing incoming requests. The following sample output from the debug aaa test command shows when the idle timer expired: Example: Device# debug aaa testJul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) quarantined.Jul 16 00:07:01: AAA/SG/TEST: Sending test request(s) to server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Sending 1 Access-Requests, 1 Accounting-Requests in current batch.Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request.Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request.Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Necessary responses received from server (192.0.2.245:1700,1701)Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) marked ALIVE. Idle timer set for 60 sec(s).Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) removed from quarantine. Step 2 Use the debug aaa sg-server selection command to determine the server that is selected for load balancing. The following sample output from the debug aaa sg-server selection command shows five access requests being sent to a server group with a batch size of three: Example: Device# debug aaa sg-server selectionJul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [3] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [2] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [1] transactions remaining in batch. Reusing server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: No more transactions in batch. Obtaining a new server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Obtaining a new least loaded server.Jul 16 03:15:05: AAA/SG/SERVER_SELECT: Server[0]