curl display folders content- Error 401 unauthorized - authentication

I have attached the screenshot of the error that occurred while trying to list the folder's content in box account using TERMINAL.Followed the link:
"http://developers.box.com/docs/"
Help me to rectify the error.
Thanks in advance.

401 Unauthorizedindicates that the access_tokenyou have is invalid or expired. Based on the comments, it sounds like you're confusing the API key AKA client_id with the access_token. The API key identifies your app, but the access_token is necessary to actually access a user's account. The process for generating an access_token is outlined here: developers.box.com/oauth

Related

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.

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

Getting error "email already in use" while requesting for authorization code in sageone API

I am trying to get access token for granting my sageone api request but before that I need to get the authorization code. But when I am trying to get one I got an error on my callback url that "email is already in use"
here is the request url
`https://www.sageone.com/oauth2/auth/central?filter=apiv3.1&client_id={{MY_CLIENT_ID}}&response_type=code&redirect_uri=http://localhost:85/test.php&scope=full_access&state=1234`
After visit above link I prompted to login to my sage account when I logged in then I redirected to the callback url which I provided in the above request and got below errors in parameters
http://localhost:85/test.php?error=Invalid+request&reason=Email+already+in+use&state=1234
any can body can suggest anything here
Email already in use usually happens in a situation, where you have logged into the Sage One/Accounting application in the browser for a different country in the past. There is a valid cookie for the user, but the application looks for the user in the wrong country.
Use this URL to reset the cookie: https://www.sageone.com/?clear. Call it before you go to https://www.sageone.com/oauth2/auth/central and this should be fixed.
Note: for more documentation about this behaviour, check out the FAQs: https://developer.sage.com/api/accounting/guides/faq/.

Adobe Sign access token invalid_request

I'm having trouble with Adobe Sign's OAuth authentication -- every time I try to get my access token with my Client ID and redirect URI, I get this message:
Unable to authorize access because the client configuration is invalid: invalid_request
This is the request that I have been making (with the proper substitution for REDIRECT and CLIENTID):
https://secure.echosign.com/public/oauth? redirect_uri=REDIRECT& response_type=code& client_id=CLIENTID& scope=user_login:self+agreement_send:account
I am fairly new to OAuth and don't understand what I'm doing wrong. Could someone please explain the issues that could result in this error message?
I was having the same problem. I solved it by including the correct shard in the URL after "secure." and before ".echosign". You identify your shard by looking at the URL where you created your application.
I found this information here.
Hope this helps.
Is OK to have spaces in that https request?
If you still have a problems with this.
I think your URL is not correct.
I using this one
https://secure.na2.echosign.com/public/embeddedWidget
for adobe widget.
Adobe require same url for OAuth
https://secure.na2.echosign.com/public/oauth
Check your domain, and try. You can create widget just to see your domain
This comment might get helpful for others who are facing issue in Adobe Sign access token invalid_request.
Developer Guide on Sign API: https://opensource.adobe.com/acrobat-sign/developer_guide/index.html
For the Outh process and the link to be used in user's browser:
https://secure.na1.adobesign.com/public/oauth/v2?redirect_uri=https://www.google.co.in&response_type=code&client_id=paste_your_client_id_here&scope=user_read:account
If any one using sandbox,
https://secure.na1.adobesignsandbox.com//public/oauth/v2?redirect_uri=https://www.google.co.in&response_type=code&client_id=paste_your_client_id_here&scope=user_read:account
Please ensure the correct environment identifier and shard. https://helpx.adobe.com/sign/using/identify-account-shard.html
https://helpx.adobe.com/sign/kb/unable-to-authorize-access-because-the-client-configuration-is-invalid-invalid-request-while-running-oauth-process.html
After pasting URL in browser and allowing the access to your API and getting code. Please use endpoint URL to get access token as below:
for developer account: https://api.na1.adobesign.com/oauth/v2/token
for sandbox account: https://api.na1.adobesignsandbox.com/oauth/v2/token

Getting Invalid Authsub Token Error 403

I am trying to authenticate my application using Blogger API but when user grant access to the application and blogger api return the token and the token i use to exchange the by sending the request on https://www.google.com/accounts/AuthSubSessionToken it return an error called Error 403 Invalid AuthSub Token. Kindly help me in this regard to debug the problem and solve it. Thanks in Advance
after doing some experiment, here it is some advice :
change secure to zero
https://www.google.com/accounts/AuthSubRequest?scope=https://gdata.youtube.com&session=1&secure=0&next=http://www.example.com
make sure you are requesting from http for and request in http again in future
https://www.google.com/accounts/AuthSubRequest?scope=http://gdata.youtube.com&session=1&secure=0&next=http://www.example.com
it's worked like a charm for me...