I tried to get a list of users through the API, but in response I got:
Missing Access 403 Forbidden (error code: 50001)
Request: https://discord.com/api/v9/guilds/{guild.id}/members;
And I was thrown out of my account, asking to verify my account.
At the same time, I accessed the server from the account that owns the server ...
MB is the fact that this is not a bot, but a live account?
Answer from comment:
Yes, using HTTP requests with user Discord accounts (user-botting) is
against Discord TOS and they can eventually terminate your account.
Create and use a bot account instead.
Related
I want to use the Linkedin API to get the company update feeds. I created the app and gave it full permissions. But I got a 403 error
Member does not have permission to get company.
Can anyone help?
I am getting 403 Access Denied error for http://www.example.com/rest/api/customers in Magento 1.9.2.4. Everything in admin side rest & admin roles and resources are proper and set to "All". Though http://www.example.com/rest/api/products is working but not able to fetch customers and getting Access Denied.
I tried with other Magento version setups also in same server but all gives 403 Access Denied error for customers and working fine for products.
Server is using SUPHP. What could be solution?
Thanks
How are you making the calls? Is it a php script or are you using something like this? You need to give this detail to identify the erroe
How to use POSTMAN rest client with magento REST api with Oauth. How to get Token and Token Secret?
I have found this tutorial is great to pinpoint where the error are ie the parameters not being encoded with the url etc
I have an application that uses OAuth 2 to access Gmail. This is working fine for most users. For some users, however, my application fails at the point of trying to read the Gmail labels, with http error 403 (forbidden). Keep in mind that previous to this API call, I have accessed the user profile successfully. Here is the call that fails:
GET /gmail/v1/users/user.name#domain.com/labels?access_token=ya29.fwI_zL1rF3xOIQcHNzpBhmjVlJhRpofkh4a9mVvwhYRo6H09qX5RNKv76zKT7e6-sEZr
I am requesting the following scopes when getting the access token, and the user has logged in to Google and accepted the request for access (and I can see this when we look at his security dashboard):
https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/userinfo.profile
https://www.google.com/m8/feeds
https://www.googleapis.com/auth/tasks
https://www.googleapis.com/auth/gmail.labels
https://mail.google.com/
Note that I just added the gmail.labels scope in at attempt to fix this.
Again, this code is working fine for most users - why do some users fail the label request?
Use the shorthand value me instead of user.name#domain.com and the user who the access token belongs to will be used automatically.
When I call linked in api method "v1/companies/{id}?format=json", I get error like "Client error response [status code] 403 [reason phrase] Forbidden". Application is authorized as group admin and it has permission: rw_company_admin. What I doing wrong?
Earlier this year, LinkedIn's API changed in several ways (detailed here: https://developer.linkedin.com/blog/posts/2015/todays-changes)
One of those changes is that you need to be an official LinkedIn company administrator to make companies API calls now, so what's likely happening to you is that the company {id} value you are submitting is one that the authenticated member is not an admin of, and as a result, the call is forbidden.
You can make the following API request to test if the current user is an admin for a given company so that you know the subsequent request will work:
https://api.linkedin.com/v1/companies/{id}/relation-to-viewer/is-company-share-enabled?format=json
Additionally, you can get a list of all the companies that a member is the admin of with this call:
https://api.linkedin.com/v1/companies?format=json&is-company-admin=true
Complete documentation is available here: https://developer.linkedin.com/docs/company-pages
For some reason, some users who try to connect through my app receive a 403 response for the /courses end point of the valence API. See below for details:
The scenario:
User can authenticate with Desire2Learn and is permitted to hit the
/whoami end point. This is always the case as the API does not allow
for this end point to require permissions.
All routes are being retrieved by a GET request
Other routes I receive success responses include:
lp/news
lp/enrollments/myenrollments
le/dropbox/folders/
Once we try to hit lp/courses I receive a 403 forbidden.
I see this route is deprecated in 10.3.0, The D2L instance I am working with is on version 10.1.0
I'm wondering if this is a group permissions issue or if my authentication is incorrect (it does work for multiple other requests)? Any ideas will be appreciated.
It looks like the /courses endpoint did not have the right authentication for my user. IT turns out though that this was for good reason. Luckily I could use the information gathered in /myenrollments instead.