blocks|key|1933377|text|我深入研究了这一点，并亲自尝试了各种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1933378|您不能通过网站UI设置此操作的权限。您必须进行API调用才能设置权限。|1933379|https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings显示用户设置的所有可能权限/范围的列表。|offset|length|1933380|https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/index.html#Update-the-name-amp-scopes-of-an-API-Key-PUT解释了如何将作用域添加到您的API键。|1933381|补充说:所以这比那更复杂。您不能使用API+Key修改API+Key，除非该key已经拥有"api_keys.update“的权限/范围。这意味着你发现自己陷入了第22条军规。您不需要使用"+authorization+:+need+{+API+}“授权头，而是需要使用”authorization+:+basic+{base64Encoded("username:password")}“这样的基本授权头进行第一次调用，以更新API键以获得该作用域。相当令人费解，现在处理起来很痛苦。听起来他们可能会在几周内推出一个更新的UI，这样我们就可以在未来避免这种小问题了。|1933382|entityMap|0|LINK|mutability|MUTABLE|url|https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings|1|https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/index.html#Update-the-name-amp-scopes-of-an-API-Key-PUT^0|0|0|0|2V|0|0|0|37|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

I dug into this and tried various things out myself.

You can't set the permissions for this to work via the website UI. You must make API calls to set the permission.

<a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings" rel="noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings</a> shows a list of all the possible permissions/scopes for user settings.

<a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/index.html#Update-the-name-amp-scopes-of-an-API-Key-PUT" rel="noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/index.html#Update-the-name-amp-scopes-of-an-API-Key-PUT</a> explains how to add scopes to your API Key.

ADDED: So this is more convoluted than that. You can't use an API Key to modify an API Key unless that key already has permissions/scope to "api_keys.update". This means you find yourself in a catch 22. Instead of using the "Authroization: Bearer {API_KEY}" authorization header you need to make the first call to update an API Key to have that scope using a basic authorization header like "Authorization: Basic {base64Encoded("username:password")}". Quite convoluted and a pain to deal with right now. Sounds like they are coming out with an updated UI hopefully in a few weeks so we all can avoid this little catch 22 in the future.

blocks|key|2635369|text|这个问题仍然存在，我要说他们的文档仍然没有完全解决这个问题。我试着修改密钥，添加了所有可能的用户配置文件范围，但我仍然无法获得我的配置文件信息，直到我尝试简单地使用基本身份验证调用它，瞧！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2635370|而且由于该调用中没有提到任何API键，所以根本不需要分配任何作用域。|2635371|curl+-X+GET+\
++https://api.sendgrid.com/v3/user/account+\
++-H+'Authorization:+Basic+base64encoded(username:password)'+|code-block|syntax|javascript|2635372|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The problem still persists and I shall say their documentation still doesn't fully address it. I tried modifying the key, added all the possible user profile scopes, but I still couldn't get my profile info until I tried to simply call it with the basic authentication and voila!

And since that call doesn't have any mentions of API key in it you don't have to assign any scope at all. 

<pre><code>curl -X GET \
 https://api.sendgrid.com/v3/user/account \
 -H 'Authorization: Basic base64encoded(username:password)' 
</code></pre>

blocks|key|1939400|text|该错误也是由于api密钥权限不足造成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1939401|https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings|offset|length|1939402|要在api+key中使用，只需：|style|CODE|1939403|Go+to+Settings+>+Api+keys+>+Edit+Api+Key+>+User+Account|code-block|syntax|javascript|1939404|维奥拉！使用API+Key作为身份验证，就像一个护身符。|1939405|curl+--request+GET+\
+--url+https://api.sendgrid.com/v3/user/profile+\
+--header+'Authorization:+Bearer+API+KEY'\
+--header+'Content-Type:+application/json'|1939406|希望这能有所帮助:)|1939407|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2V|0|0|2|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|F|3|G|5|6|7|16|8|@$D|17|E|18|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|C]]]]

This error is also caused due to insufficient permissions for api key. 

<a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings" rel="nofollow noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html#User-Settings</a>

In order to use with <code>api key</code> just : 

<pre><code>Go to Settings &gt; Api keys &gt; Edit Api Key &gt; User Account
</code></pre>

Viola! works like a charm with API Key as Auth.

<pre><code>curl --request GET \
 --url https://api.sendgrid.com/v3/user/profile \
 --header 'Authorization: Bearer API KEY'\
 --header 'Content-Type: application/json'
</code></pre>

Hope this helps :)

blocks|key|27795|text|根据我自己的测试(找不到任何官方的东西)，看起来SendGrid电子邮件的免费版本只允许通过API发送电子邮件。为了通过API进行任何其他类型的调用，您需要将您的帐户升级为付费帐户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|27796|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Based on my own testing (can't find anything official) it looks like the free version for SendGrid Email only allow sending emails through the API. In order to make any other types of call through the API, you will need to upgrade your account to a paid one.

blocks|key|1933426|text|旧版API不起作用。使用新的接口|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1933427|我不知道它是否解析到某人，但我尝试使用此文档添加一个联系人到sendgrid，得到{"errors":{"field":null，"message":"access+forbidden"}}：|1933428|https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html#Add-Single-Recipient-POST|1933429|POST+POST+https://api.sendgrid.com/v3/contactdb/recipients+HTTP/1.1|code-block|syntax|javascript|1933430|经过更多的搜索，我注意到了一个新的文档(相同版本的API+v3)，但使用了非常不同的API方法：|1933431|https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact|1933432|PUT+https://api.sendgrid.com/v3/marketing/contacts|1933433|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|G|0|0|0|33|0|0|0|0|0|1U|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|J|3|K|5|L|7|1A|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1B|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|S|3|T|5|L|7|1G|8|@]|D|@]|E|$M|N]]|$1|U|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|I]]|11|$5|X|Y|Z|E|$10|R]]]]

Legacy API doesn't work. Use new API

I don't know if it resolve to someone, but I tried to add a contact to sendgrid using this doc getting {"errors":[{"field":null,"message":"access forbidden"}]}:

<a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html#Add-Single-Recipient-POST" rel="noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/Marketing_Campaigns/contactdb.html#Add-Single-Recipient-POST</a>

<pre><code>POST POST https://api.sendgrid.com/v3/contactdb/recipients HTTP/1.1
</code></pre>

After search a bit more I noted a new documentation (same version API v3) but with very different API methods:

<a href="https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact" rel="noreferrer">https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact</a>

<pre><code>PUT https://api.sendgrid.com/v3/marketing/contacts
</code></pre>

blocks|key|27115|text|我正好遇到这个问题，我这里是我的解决方案:你需要创建Auth+Sender：https://app.sendgrid.com/settings/sender_auth用于测试，只需创建一个简单的单发件人验证，对于生产，你应该创建一个基于你的域的帐户。我使用免费版本，我可以在修复后发送我的电子邮件。请注意，电子邮件可以转到垃圾邮件收件箱。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|27116|entityMap|0|LINK|mutability|MUTABLE|url|https://app.sendgrid.com/settings/sender_auth^0|2P|6|12|19|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

I just meet this issue, and I here is my solution: You need to create the Auth Sender: <a href="https://app.sendgrid.com/settings/sender_auth" rel="nofollow noreferrer">https://app.sendgrid.com/settings/sender_auth</a>
For testing, just create a simple Single Sender Verification, for productions, you should create a account base on your domain. 
I use free version and I can send my email after fix this. Notice that, email can go to Spam inbox.

blocks|key|1933469|text|正如Khurram+Tahir提到的，这是，而不是与免费版本相关的。为了符合合法的发送行为和信誉，SendGrid要求我们验证我们的发件人身份(即“发件人”电子邮件地址)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1933470|请参考下面的文档，该文档清楚地列出了验证步骤。https://sendgrid.com/docs/ui/sending-email/sender-verification/|1933471|我也面临着(403访问禁止)的问题，我已经按照上面的步骤解决了我的问题，并能够发送电子邮件。|1933472|entityMap|0|LINK|mutability|MUTABLE|url|https://sendgrid.com/docs/ui/sending-email/sender-verification/^0|L|C|0|N|1R|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

As mentioned by Khurram Tahir, this is NOT related to the free version. In order to meet legitimate sending behavior and reputation, SendGrid require us to verify our sender identifiers (i.e) the &quot;From&quot; email address.
Please refer the below document which lists the verification steps clearly.
<a href="https://sendgrid.com/docs/ui/sending-email/sender-verification/" rel="nofollow noreferrer">https://sendgrid.com/docs/ui/sending-email/sender-verification/</a>
I also faced the (403 access forbidden) issue, i have followed the above steps which resolved my issue and able to send email.

blocks|key|27878|text|我相信，从2020年11月起，Sendgrid修复了初始权限，新的error...so密钥应该具有正确的权限。即使这不是问题所在，However...some应用程序接口调用仍然会报告“禁止访问”错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|27879|以下面的查询为例：|27880|curl+--request+POST+--url+https://api.sendgrid.com/v3/categories/stats+--header+'Authorization:+Bearer+secretapikey'+--header+'Content-Type:+application/json'+--data+'{"start_date":+"2015-01-01","categories":+['Email+123']}'|code-block|syntax|javascript|27881|使用access+forbidden..even会失败，尽管您的api+key有权限使用它。相反，问题是Sendgrid需要你使用GET而不是POST来处理一些请求(愚蠢的)，...and参数必须是urlencoded的。以下代码可以正常工作。|27882|curl+--request+GET+--url+'https://api.sendgrid.com/v3/categories/stats?start_date=2019-01-01&categories=Email%2520123&aggregated_by=month'+--header+'Authorization:+Bearer+secretapikey'+--header+'Content-Type:+application/json'|27883|如果您在文档(例如https://sendgrid.com/docs/API_Reference/Web_API_v3/Stats/categories.html)中看到使用GET+variables...chances的请求，那么您的CURL请求也需要这些内容。|offset|length|27884|entityMap|0|LINK|mutability|MUTABLE|url|https://sendgrid.com/docs/API_Reference/Web_API_v3/Stats/categories.html^0|0|0|0|0|0|9|20|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

To any wayward Googlers that find this...I believe as of November 2020 Sendgrid fixed the initial permission error...so new api keys should have the correct permissions. However...some api calls will still report a &quot;Access forbidden&quot; error even if that is NOT the issue.
For example take this query:
<pre><code>curl --request POST --url https://api.sendgrid.com/v3/categories/stats --header 'Authorization: Bearer secretapikey' --header 'Content-Type: application/json' --data '{&quot;start_date&quot;: &quot;2015-01-01&quot;,&quot;categories&quot;: ['Email 123']}'
</code></pre>
That fails with access forbidden..even though your api key DOES have permission to use this. Instead the issue is that Sendgrid needs you to use GET instead of POST for some requests (stupid)...and the url parameters must be urlencoded. The following does work correctly.
<pre><code>curl --request GET --url 'https://api.sendgrid.com/v3/categories/stats?start_date=2019-01-01&amp;categories=Email%20123&amp;aggregated_by=month' --header 'Authorization: Bearer secretapikey' --header 'Content-Type: application/json'
</code></pre>
If in the documentation (eg <a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/Stats/categories.html" rel="nofollow noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/Stats/categories.html</a>) you see the request using GET variables...chances are you'll need these for your CURL request as well.

blocks|key|27168|text|如果你像我一样，从节点库文档中获得了这里，正如Marius上面所说的，你的2021帐户将不能与节点客户端库中列出的旧api一起工作。使用node客户端，但使用此处的新api：https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|27169|所以在2021年是可行的：|27170|const+client+=+require('@sendgrid/client');
client.setApiKey(sendgrid_api_key)

const+uploadRequest+=+{
++++++++body:+{
++++++++++list_ids:+[listId],
++++++++++contacts:+[
++++++++++{
++++++++++++email:+email,
++++++++++++first_name:+firstName
++++++++++}
++++++++]},
++++++++method:+'PUT',
++++++++url:+'/v3/marketing/contacts'
++++++}
const+uploadResponse+=+await+client.request(uploadRequest)|code-block|syntax|javascript|27171|对于大多数不一致的文档，Sendgrid可能会以这种速度夺得Paypal的桂冠:)|27172|entityMap|0|LINK|mutability|MUTABLE|url|https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact^0|2F|1U|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

If like me you got here from the node library docs, as Marius said above your 2021 account won't work with the old api listed in the node client library. Use the node client, but with the new api here:
<a href="https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact" rel="nofollow noreferrer">https://sendgrid.api-docs.io/v3.0/contacts/add-or-update-a-contact</a>
so works in 2021:
<pre><code>const client = require('@sendgrid/client');
client.setApiKey(sendgrid_api_key)

const uploadRequest = {
 body: {
 list_ids: [listId],
 contacts: [
 {
 email: email,
 first_name: firstName
 }
 ]},
 method: 'PUT',
 url: '/v3/marketing/contacts'
 }
const uploadResponse = await client.request(uploadRequest)
</code></pre>
Sendgrid may take Paypal's crown for most inconsistent documentation at this rate :)

blocks|key|4749151|text|对我来说，我试着调用POST+/v3/+marketing+/contacts，但这个端点似乎是用于新的营销。我们公司使用传统的市场营销手段，我不得不使用其他终端设备|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4749152|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me, i tried to call POST /v3/marketing/contacts but seems that this endpoint is for new marketing. Our company use legacy marketing to i have to use other endpoints

The following API request: 

<pre><code>curl --request GET \
 --url https://api.sendgrid.com/v3/user/profile \
 --header 'Authorization: Bearer API KEY'\
 --header 'Content-Type: application/json'
</code></pre>

From the docs: <a href="https://sendgrid.com/docs/API_Reference/Web_API_v3/user.html" rel="noreferrer">https://sendgrid.com/docs/API_Reference/Web_API_v3/user.html</a>

Results in a HTTP 403 response with the following body:

<pre><code>{"errors":[{"field":null,"message":"access forbidden"}]}
</code></pre>

I went to Settings -> API Keys and clicked on 'Edit details' to view the permissions granted to my API key and, as far as I can tell, there isn't any permission that I can grant (or revoke) that seems related to 'user profile'. 

Just to be on the safe side, I have configured every single permission to 'Full Access' (when available) or to 'Read Access' if 'full access' is not available but I am still getting this HTTP 403 error.

What is the permission I need to grant to my API key in order to be able to retrieve my user profile?

sendgrid error "Access forbidden" when trying to GET user profile API

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

以下接口请求如下：curl --request GET \     --url https://api.sendgrid.com/v3/user/profile \     --header 'Authorization: Bearer API KEY'\     --header 'Content-Type: app...

问尝试获取用户配置文件API时，sendgrid出现“禁止访问”错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试获取用户配置文件API时，sendgrid出现“禁止访问”错误EN