403 Access Denied for customers in Magento REST API - api

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

Related

Using API token to access the CPanel UAPI returns access denied

I am trying to dynamically create email accounts for users via the CPanel API. According to the documentation here, an access token can be used to call the API endpoints. I have an access token generated already but I keep getting acccess denied. I already tried generating another access token just incase the first one was wrong but Its still the same error.
My curl command is in this format as specified in the docs:
curl -H'Authorization: cpanel username:U7HMR63FHY282DQZ4H5BIH16JLYSO01M' 'https://example.com:2083/execute/Email/add_pop?email=newuser&password=12345luggage'
What could I be doing wrong please ?

Access Denied Error In Post Shipment APIs

I'm working on Restful API for Post shipment. When I am checking it on Postman It showing me Access Denied Error. Can Anyone Help me ?
https://api.postshipping.com/api2/tracks?ReferenceNumber=************
enter image description here
Most likely you are missing a session cookie / authentication at all to access this endpoint. Please check, if there is any authentication required and if so, if the user has enough rights to access this data.

Apache nifi getTwitter Processor returning 403 forbidden

I want to use Apache Nifi to track real time tweets
i pasted in my keys correctly but all requests return this error :
19:15:20 UTC ERROR
GetTwitter[id=59b5cb18-017e-1000-a6a2-991a653ec138] Received error HTTP_ERROR: HTTP/1.1 403 Forbidden. Will attempt to reconnect
i dont know where the problem is from.
thank you.
403 Forbidden means the Twitter API is rejecting your request - your access keys could be incorrect, or you might not have the right access rights for the endpoint you're accessing.
The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why.
Check that your developer account includes access to the endpoint you’re trying to use. You may also need to get your App allowlisted (e.g. Engagement API or Ads API) or sign up for access.
From https://developer.twitter.com/en/support/twitter-api/error-troubleshooting
Make sure you follow the advice from Twitter here and make note of:
With Essential access, you are only able to make requests to the Twitter API v2 endpoints, and not the v1.1 or enterprise endpoints. You are limited to 500K Tweets/month, and unable to take advantage of certain developer portal functionality such as teams and access to additional App environments
There are limits on what you can do with the Essential access level. See here.
If that doesn't help - please include a screenshot of your GetTwitter config and your version of NiFi.
If it raises 403 error while using GetTwitter processor in nifi.
API Key & consumer key aren't only a problem. Change the Twitter endpoint field while configuring the GetTwitter processor from
Filter Endpoint
to
Firehose Endpoint
In the field of twitter endpoint
Probably this will work!!

Permission denied when try to fetch records from zoho people

I am trying to fetch records from zoho people API .. For this i am using POSTMAn. I successfully create token in postman and when i try to apply this link in get field then this shows an error "permission denied" i tried from past few days but did not come up with solution
token i successfully created in zoho people
Then i use that token in postman like this
but this shows an error
{
"error": "Permission denied"
}
what should i do ? any help please
I tried your steps but I found that in my case I can access this API
I created my access token from here
Zoho people settings page
Zoho people > Settings > Zoho people API
For API reference check this page
https://www.zoho.com/people/help/api/attendance-api.html#2
Here are my request and response
request
response
In Postman, go to File > Preferences and make sure the "SSL certificate verification" option is ON, as well as the "Send Postman Token header" and "Automatically follow redirects" options. These are the settings I have in my install of Postman and am able to make requests to Zoho API. I suspect the problem may be with how your install of Postman is handling SSL verification.
you need to give permission to read, write, edit ,from the zoho application first

Valence will give 403 on a GET lp/courses to some student users

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.