sendgrid-api-v3

问题 I am trying to create Campaigns by using Sendgrid V3 API. if i use Try it out tool it shows like Error message like "authorization required" even though Authorization Bearer value(API KEY) given, if i hit the same in Postman it gives error response like "access forbidden". Is this Sendgrid API Issue or am i missing anything? and one more question here is shall we try campaign related operations by using trial account? Note : Same API key is working fine for some other operations like List

来源： https://stackoverflow.com/questions/64470449/nodejs-nodemailer-sendgrid-smtp-username-password-to-api-key-using-existing

问题 I have setup an endpoint for sendgrid to send event notifications. However, the server is setup with basic authentication and the events don't come through because they are not authenticated. How can I authenticate these event webhooks by SendGrid or whitelist SendGrid? 回答1: You can use basic authentication when setting up the HTTP POST URL by setting it to a value like https://user:password@this.is.my.test/listening/endpoint Where "user" is the basic authentication user name and "password"

问题 I am trying to send the emails via Sendgrid using v3 API using postman, I have created 3 separate variables in 3 different requests, I want to pass all those 3 variables in a single mail, for that I have used below sendgrid https://api.sendgrid.com/v3/mail/send with below body { "personalizations": [ { "to": [ { "email": "testing@test.com", "name": "API Testing" } ], "subject": "API testing successful" } ], "from": { "email": "noreply@testApi.com", "name": "API Testing" }, "content": [ {

问题 I have a dynamic email template for sending a user a unique token link to reset their password. I assign the link to a field named 'link' in the dynamic_template_data section of my personalizations in my request object. When I receive the email, my anchor tag has no href attribute. Here is my request object: { method: "POST", url: "/v3/mail/send", headers: { "content-type": "application/json" }, body: { personalizations: [ { to: [{ email: email, name: name }], dynamic_template_data: { link:

问题 Have been trying to create a campaign with SendGrid API. Adding lists, recipients, and recipients to lists all works fine. However, as soon as I try to add a new campaign my curl response is: <!-- This is a random-length HTML comment:

问题 Have been trying to create a campaign with SendGrid API. Adding lists, recipients, and recipients to lists all works fine. However, as soon as I try to add a new campaign my curl response is: <!-- This is a random-length HTML comment:

问题 Versioning in SendGrid allows API clients to make template requests only by template ID documented here, however, only one version of a template can be "Active" at a time. Obviously, the template used for our production applications needs to always be set to active, but what about adding a new template version we use in an upcoming release? How can I leverage template versions to test this "Inactive" version in our test environment? The issue was discussed here, but it seems to just be closed

问题 I want to send a transactional mail via Sendgrid when a user registers (I use devise for authentication). I had this working fine in my_mailer.rb using SMTP as follows: def confirmation_instructions(record, token, opts={}) # SMTP header for Sendgrid - v2 # headers["X-SMTPAPI"]= { # "sub": { # "-CONFIRM_TOKEN-": [ # token # ] # }, # "filters": { # "templates": { # "settings": { # "enable": 1, # "template_id": "1111111-1111-1111-1111-111111111111" # } # } # } # }.to_json However, prompted by

问题 I am trying to send email thru fire base cloud function. I am getting log that email is sent but I don't see any email. Below is the code and the logs. Where do I begin to troubleshoot? 'use strict'; const functions = require('firebase-functions'); const nodemailer = require('nodemailer'); const SEND_GRID_API_KEY = functions.config().sendgrid.key const sgMail = require('@sendgrid/mail'); sgMail.setApiKey(SEND_GRID_API_KEY); // Your company name to include in the emails // TODO: Change this to