Case:
I bought Uber Event with promocodes.
Made a deep link from my app to Uber:
https://m.uber.com/ul/?client_id=xxxyyy-zzz&action=applyPromo&promo=existingtestpromo
Set up an API webhook in the Uber Dashboard to receive POST at https://45.55.254.130/uber/webhook/ (no domain yet and self-signed SSL)
User followed the link and made a ride. He finished the ride ok.
No webhook received at all(django+uwsgi logs empty on that url). I also tested that url manually sending POST request from code - it works.
Are the webhooks used at all when using deep links with promocodes?
Webhooks do not get sent when you use the deeplinks (promo code or set pickup). You can receive webhooks when you make a ride request using POST v1/requests or when you have the all_trips scope.
Here's information about making a ride request using the API: https://developer.uber.com/docs/rides/sdks/introduction
And here's information about all_trips scope (the feature is called Trip Experiences): https://developer.uber.com/docs/rides/tutorial-trip-experiences-getting-started
Related
I am working with one of the Pilot endpoints trying to implement the new CyberSource recurring billing for a customer of ours.
I had a discussion with CyberSource late last year, and was provided the API reference link to these new endpoints. The API endpoint is https://apitest.cybersource.com/rbs/v1/subscriptions.
I noticed that when testing these endpoints in the API reference page, they would work and the subscriptions were created in our Sandbox account.
When testing this endpoint in our applications integration however, I am seeing a 401 unauthorized on each request. I see the same thing when testing in Postman, but not when testing directly in the API reference.
Is there something I need to include in the request header or otherwise in order to make these calls work?
I am using webhook to create bot for page. I got everything but not getting where to get Callback URL
I think you're misunderstanding the concept of webhooks. The Callback URL is simply the location that you want Facebook to deliver messages to.
For example: if you are running a server at https://my_awesome_service.com and you want it to receive facebook updates, you would first create a route (let's say /v1/facebook_subscriptions) in your service. Once that's ready, you would insert https://my_awesome_service.com/v1/facebook_subscriptions into that Callback URL field. Facebook will then do a GET on that URL, which your server must reply to correctly. After that's done, Facebook will start sending you POST's, based on the subscription fields you set up.
There's a lot more information about this in the Facebook API Docs.
Callback URL(s)
A callback URL indicates where the user is to be redirected after a successful sign-in. Choose at least one callback URL, and it should:
Be an absolute URI.
Be pre-registered with a client.
Not include a fragment component.
See OAuth 2.0 - Redirection Endpoint.
Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.
App callback URLs such as myapp://example are also supported.
We are busy looking at Uber Ride API and would like to find out the following:
Is all_trips scope applicable if OAuth authorized user is an Uber driver?
Will Webhook invoke events everytime when a driver accepts/cancels/completes a trips?
will Webhook be invoked during a real trip while the app is under development or Only work in Sandbox?
No. The all_trips scope only works for riders.
Yes. Every trip status change triggers a webhook. Possible statuses changes are:
processing
no_drivers_available
accepted
arriving
in_progress
driver_canceled
rider_canceled
completed.
(List pulled from here, according to the webhooks documentation here).
Yes. If you grant your app the all_trips scope, the Uber API will send webhooks to the URL you have registered at developer.uber.com/dashboard for every trip you take, i.e. sandbox and real trips alike. Note that there is currently no way to flag an Uber app as "in development" or "in production".
I'm prototyping a trip experience. In debug we have a button that requests an in_progress ride to work with. Everything seems to work ok.
However, a release build (hitting the real API rather than sandbox) I get no trips back.
We have requested: request and all_trips scope.
We have the test users' uber accounts added to the developer portal.
Requesting the scopes is working, we're takin to the site and it asks for the appropriate scopes, the app is listed in the user's profile.
Any ideas? Is there a region limitation, for example?
Could you provide some more details on the the exact flow you are following and what endpoints you are hitting?
If you make a GET request to nonsandbox /v1/requests/current with an access token for a user that is on a trip, what response do you get back?
I'm making a ride request via the Uber API. I successfully make a request and get a response that it's in the Processing state. I then open my Uber app to watch until it goes into the Accepted state, but it never gets there. After about 15 seconds of processing, it pops up with a weird error message that I've never seen before in the Uber app: "All vehicles are currently in use. Please call (206) 622-6500". I called the phone number just to see, and it's the number for Yellow Cab in Seattle.
I try to make a request using the Uber app as normal, and it works fine.
I'm not making my ride request using the API sandbox; I'm actually trying to request a ride for myself using the limited access request scope for my personal account.
There's not any code to associate with this since I'm making a request successfully. Uber API support has requested that I ask a question on StackOverflow instead of reaching out to them directly.