I am trying to do an auto-booking of a cab from my code for uber, only for me.
I have my clientID, client Secret and Access Token. How to use them so that i can fire a request and monitor the status whether has been booked or not? Or if no cabs are available it would retry at specific intervals unless a cab gets booked.
Please guide me.
In the meantime while i am trying to fire a v1/me, i am getting 401 Unauthorized.
Did you try following the Authentication tutorial to understand if the requests you fire are as expected?
Also, you're getting down voted because there is code or anything that would enable us to help you debug this issue. If the hints in the tutorial do not help, please provide more details on the headers you add. You need to have the authorization header: Authorization: Bearer <YOUR_ACCESS_TOKEN> with a valid access_token.
Related
I am using BinarySecurityToken for OTA_AirRulesRQ, but I am getting USG_AUTHORIZATION_FAILED. I used the same token for BargainFinderMaxRQ and it worked. Is it some problem with the SOAP request I am sending or access to this method is not authorized form my PCC ?
Also I am able to hold PNR and Issue ticket with same credentials
Please Suggest
You should contact the API helpdesk providing your credentials
Do you point it to the according endpoint. E.g. getting creds from prod/testing and using it in prod/testing?
Can you post the message you are trying to send including headers. You can block out Pcc information, but it would help to see the message. It may be something simple you are overlooking and at the very least I could duplicate the call on my test bench and try to to duplicate the issue.
I'm a beginner with this while magento/postman thing. Right now I'm trying to get a token and token secret from magento using postman, but I've been stuck for days now and I don't know where else to look for solutions.
I'm using a guide posted by Franklin Strube (user from this forum), but I can't get past the first step since the response I get is "oauth_problem=nonce_used".
I've already checked the following:
- No special ports re being used to connect to my webpage
- REST roles, attributes and clients have been set up correctly in order to have access to the APIs.
- My user has already a key and a secretm which I'm using to send the request via Postman through the GET method.
This is how my postman looks right now:
Please, I'd appreciate any help you can provide me.
Thanks a lot!
I'm going step-by-step Nest REST Quick Guide and now blocked with error response during attempts to obtain an access token.
Response is:
{"error":"client_not_active","error_description":"client is not active","instance_id":"here_is_something_looks_like_guid"}
I've checked Error Messages Guide, and it helps me a lot to understand that "Client not active". Useful, huh?
So which client and how to activate it?
I have a home simulator working, also I've registered a so-called 'product', which I want to develop (so I have Product ID, Product Secret, Authorization URL and Access Token URL).
[Upd]
For all operations I've used curl.
However with Firefox addon which sends POST data I'm able to obtain the access_token. So I keep the question, but so far will stick to browser.
This means the your product/client has been deactivated, most likely due to a violation of the Terms of Service. Is the problem consistently occurring?
I face a problem today regarding the connectivity with Orion public instance #http://orion.lab.fi-ware.org:1026/ngsi10/contextEntities/{entity_id}. While, two days ago, I got always connection to the orion public instance, always by using the same Authentication Token, I got from FI-WARE, Today when I'm trying to connect I get an error: "GET http://orion.lab.fi-ware.org:1026/ngsi10/contextEntities/urn:smartsantander:testbed:3337 returned a response status of 401 Unauthorized".
I was and continue to use the Jersey REST API so as to connect with NGS10 Orion REST API Implementation.
Is there any idea about what I have to do to solve the problem? Is this a problem in Orion Server side with the Authentication Service?
Thank you in advance!
Probably the token has expired. You can re-generated a fresh token runing the token_script.sh script, as described in the following document.
EDIT: the normal behaviour of the system is to cancel the token from time to time, so the best approach is regenerate it with a given periodicity (e.g. 24 hours). However, note that although you can manually regenerate the token and recofigure your application to use the new one as described above, it is better to program your application to do it automatically.
Please, have a look to the OAuth course in FI-WARE education platform and the Refresh Token section in the OAuth 2.0 RFC for more information.
My application, created today, runs fine when I use it with my account. On any other account however, the following error is sent back as a response:
message: "(#298) You must be a developer of the application"
type: "OAuthException"
The exact code I'm using to send the request is this:
FB.api('/me/threads', {limit: 1000}, function(response){ ....
I have found someone experiencing the same problem, but the response he accepted didn't really provide any useful information. ( Reading over inbox, I get error #298).
Anyone have a clue on how to solve this? Would be greatly appreciated!
I'm guessing you have the read_mailbox permission?
Try accessing the /me/inbox connection instead?
Facebook tells you (from http://developers.facebook.com/docs/reference/api/thread/):
Please note: We are in the process of making the new messages system
available to all users, at which point this API will replace the
/inbox/ Graph API endpoint. We are providing early access to this API
for registered developer accounts only until the new messaging system
is broadly available. You should use the /inbox endpoint for
production applications at the current time.
That is, only the current apps developers will be able to use the threads-connection for now (but it will be available later).
It looks like your other account doesn't have a developer license/flag/attribute, thus failing the authentication check.