403 access forbidden

[MatteoGioioso]

Issue Summary

I am trying to add a Single Recipient to sendgrid following these instructions:
https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html#Add-Single-Recipient-POST
But when I try to hit that endpoint I receive 403 access forbidden

{
  "message": "FORBIDDEN",
  "code": 403,
  "response": {
    "headers": {
      "server": "nginx",
      "date": "Tue, 30 Jul 2019 00:31:22 GMT",
      "content-type": "application/json",
      "content-length": "56",
      "connection": "close",
      "access-control-allow-methods": "HEAD, GET, PUT, POST, DELETE, OPTIONS, PATCH",
      "access-control-max-age": "21600",
      "access-control-expose-headers": "Link, Location",
      "access-control-allow-origin": "*",
      "access-control-allow-headers": "AUTHORIZATION, Content-Type, On-behalf-of, x-sg-elas-acl, X-Recaptcha, X-Request-Source",
      "content-security-policy": "default-src https://api.sendgrid.com; frame-src 'none'; object-src 'none'",
      "x-content-type-options": "nosniff",
      "strict-transport-security": "max-age=31536000",
      "x-ratelimit-remaining": "2",
      "x-ratelimit-limit": "3",
      "x-ratelimit-reset": "1564446684"
    },
    "body": {
      "errors": [
        {
          "field": null,
          "message": "access forbidden"
        }
      ]
    }
  }
}

I am already using the @sendgrid/mail and I have no problem with that.

Steps to Reproduce

I am trying to call the API endpoint from a serverless function

sendgridClient.setApiKey(tokens.SEND_GRID)

My API key has full access

exports.saveContact = functions.https.onRequest(async (req, res) => {
  cors(req, res, async () => {
    const { email } = req.body
    const request = {}
    request.body = [{ email }]
    request.method = 'POST'
    request.url = '/v3/contactdb/recipients'

    try {
      const [response] = await sendgridClient.request(request)
      res.status(200).send(response)
    } catch (error) {
      res.status(500).send(error)
    }
  })
})

Technical details:

• sendgrid-nodejs Version: 6.4.0
• Node.js Version: 11.15.0

PS: I have a Blaze pay as you go plan with firebase and cloud functions

[MatteoGioioso]

Any update on this?

[MatteoGioioso]

at the moment I am unable to save contacts, any help?

[rafaelvicio]

same problem

[rafaelvicio]

From what I've verified, this is because our account is on the free plan, which doesn't allow us to use this API.

[JClackett]

I am a paying customer and am getting a 403 on this endpoint:

/v3/contactdb/lists/{id}/recipients

any suggestions?

[wcandillon]

I am also suffering from the same issue. My API key is unrestricted and I am on the free plan. @JClackett seems to suggest that upgrading to the paid tier won't solve the issue.

[ZenPylon]

Same issue here for the endpoint v3/contactdb/recipients. I tried created a new API key with full access, and still no luck. This is on the paid "Pro" plan. I have no issue sending mail with the same key. This really seems like a bug on SendGrid side.

[wcandillon]

I haven't tried it yet but their support seemed to suggest to do a PUT instead of a POST?

[ZenPylon]

Thanks for the suggestion - just tried that, but no luck. 😕

[aroach]

I was able to create contacts using the straight API and "Try It Out" feature, so the backend seems to be working as expected. Contacts API - Recipients <https://sendgrid.api-docs.io/v3.0/contacts-api-recipients>

…

On Tue, Sep 24, 2019 at 2:02 PM Andrew Decker ***@***.***> wrote: Thanks for the suggestion - just tried that, but no luck. 😕 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#957?email_source=notifications&email_token=AARP5MW4NQ6KFDDWJE2F7A3QLJW4DA5CNFSM4IHXNHK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7PT7JY#issuecomment-534724519>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARP5MX5PBM7KL7JHKUUYBDQLJW4DANCNFSM4IHXNHKQ> .

[ZenPylon]

Thanks for your comment, @aroach. Perhaps the issue lies in the way API keys are being provisioned? The API key I'm using has "Full Access", so if the endpoint itself is working, then there must be something wrong with the key.

[aroach]

We’re you able to succeed using the try it out with the same API key?

…

On Sep 24, 2019, 6:30 PM -0600, Andrew Decker ***@***.***>, wrote: Thanks for your comment, @aroach. Perhaps the issue lies in the way API keys are being provisioned? The API key I'm using has "Full Access", so if the endpoint itself is working, then there must be something wrong with the key. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ZenPylon]

It unfortunately gives the same 403.

[aroach]

I was wondering if perhaps because the API key I created a while ago, maybe something had changed with API keys. But, I created a fresh one and it still worked for me. Perhaps triple check your API key permissions. I was able to get it to 403 by disabling the Marketing Campaigns scope.

…

On Tue, Sep 24, 2019 at 6:45 PM Andrew Decker ***@***.***> wrote: It unfortunately gives the same 403. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#957?email_source=notifications&email_token=AARP5MUIB6UFN6WXDF3G2OTQLKYD7A5CNFSM4IHXNHK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7QHCKY#issuecomment-534802731>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARP5MVDNGXY3AETAFQDRODQLKYD7ANCNFSM4IHXNHKQ> .

[aroach]

Maybe @thinkingserious or @ben-grid have some thoughts here.

[ZenPylon]

Thanks for your persistence. I created a new key in both our staging and production SendGrid accounts with full access, but the 403 error persists in the "Try it Out" section for both. Hoping one of the others you've brought to the conversation might be able to help. 🙏

[MatteoGioioso]

I remember I have created a separated key just to call that endpoint and a new one with full access to temporarily test that issue, but still did not work.

[wcandillon]

This the request that I am doing now:

  const request = {
    method: "PUT",
    url: "/v3/marketing/contacts",
    body: {
      contacts: [
        {
          email
        }
      ]
    }
  };
  await client.request(request);

[ZenPylon]

@wcandillon Thanks for the code snippet. I just got a response from SendGrid support that confirms that this is the correct endpoint to use. Response below:

POST /v3/contactdb/recipients is an endpoint associated with our Legacy Marketing Campaigns product. I'm able to see on our backend that your account does not have access to due to it the Legacy experience, having been created after the launch of the New Marketing Campaigns Experience. I feel this is the most likely source of the unexpected error.

In this case the PUT /marketing/contacts call will be the equivalent call for the New Marketing Campaigns experience. https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact

I was able to use this endpoint successfully.

[alfredoreduarte]

Hi, I've tried the default example given at
https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact
with a fresh API key and all I'm getting is "invalid JSON", even though the JSON payload hasn't been edited, it's just the default example.

Anyone else going through this?

[mbosek]

@alfredoreduarte I have the same

[ben-grid]

Hey @alfredoreduarte @mbosek

I'm a product manager at SendGrid, though I don't own this part of the product.

I checked it out and am similarly unable to get a PUT to work either with the example or based on the field requirements in the doc. I'm following up with the PM/Team who owns this part of the product to see what's up and will circle back with you here once I know more.

[ben-grid]

@alfredoreduarte @mbosek

This is fixed now. We just had the tech powering our "Try it out" feature misconfigured so it wasn't consuming JSON properly. Works now!

Thanks for reporting the issue!

[alfredoreduarte]

Thanks! Now I'm able to add contacts. However, it's been like six hours since I successfully added one and it still isn't showing up on my list. I guess I'll report this by opening a different issue.

[alfredoreduarte]

@ben-grid turns out the /v3/marketing/contacts endpoint does not support an ID field for users, although the "try it out" tool includes that field as an example.

Please get someone to update the example :)

[alfredoreduarte]

This closes #1004

[ben-grid]

@alfredoreduarte Ah yeah, good call, thanks. I just updated it, which will go out with our next deploy. Thanks for the heads up!

[mrillstone]

still having this problem with POST mail/send feature in the API docs, any update?

[mavrick]

none of my contacts are updating or being added when using the /v3/marketing/contacts endpoint. it just returns a job_id and then nothing is ever updated when i check the dashboard.

attempted to use the contactdb/recipients endpoint and it just results in a 403 error.

[mavrick]

A follow up on this.

When using custom fields, if your field is set to text, you can only send text. Ensure your types match, otherwise it will enver update. Being unable to check the job_id or get any kind of field validation is the problem here

[Promessed]

I also have the same issue with POST mail/send feature in the API docs, any update? @ben-grid

[RobSwish]

Me to, I feel like my code should work, bit I just keep getting a 403 when sending an email with node.

[childish-sambino]

@RobSwish Could you provide a code sample that illustrates this issue and also the response body?

https://github.com/sendgrid/sendgrid-nodejs/blob/master/docs/use-cases/success-failure-errors.md

[tjoudeh]

Same happening with the C# SDK (NuGet SendGrid) too, this is what I'm using currently:

 var client = new SendGridClient(apiKey);
            var from = new EmailAddress(fromEmail, fromName);
            var to = new EmailAddress(email);

            var msg = MailHelper.CreateSingleEmail(from, to, subject, message, message);

            // Disable click tracking.
            // See https://sendgrid.com/docs/User_Guide/Settings/tracking.html
            //msg.SetClickTracking(false, false);

            var response = await client.SendEmailAsync(msg);

            return response;

[YJChan]

I'm able to do that by verify the sender email. Read this guide.
https://sendgrid.com/docs/for-developers/sending-email/sender-identity/
They need you to verify the sender email before you can send out anything. If you just want to test out the sending feature, you can try to use your personal email to setup first.
This step is a not included in the getting started guide which I think is not very user friendly.

[jayjonah8]

I am able to get a successful response and a job_id when I hit thehttps://api.sendgrid.com/v3/marketing/contacts end point but on my dashboard there are no contacts showing up. I have the correct list id but nothing seems to work