We're working on a new web application using the Uber API and had a couple questions concerning the use of 'fare_id'
Is “fare_id” is a required parameter for POST /requests Api call? Can we pass empty value for fare_id and book a request?
What should be passed for “fare_id” in the ride request api for product that involves Surge Pricing?
Thanks
The Fare ID was introduced with the concept of Upfront Fares (as part of the announcement of v1.2 endpoints of the Uber API). Upfront fares replace the concept of surge pricing to follow a dynamic pricing concept. You have to pass such an ID if you use v1.2 endpoints. However, if you are still using v1.0 of the Uber API, the Fare ID is optional and mostly useful for UberPOOL.
To obtain a Fare ID, you have to follow the best practices of Upfront Pricing.
We successfully tested in the sandbox with setting fare_id to null in the cases described (using the java sdk).
Related
I'm trying to use UberAPi to request rides while not requiring an authentication from the end user (rider).
My company should be responsible for the payments from such rides, and would only request that a driver appears at point A at such time, and deliver someone to point B.
Uber business does have all the features needed for such an integration: Usage reports, expense codes, and else, but I see no way of doing this without either an SSO or OAuth.
No, it is not currently possible to use the api for such a use case. You might want to consider using Uber Central.
REST API documentation is very confusing right now on the yodlee site, especially for the IAV features and the developer information (flows vs API references vs Integration Guide) does not seem to be current and coherent regarding IAV features vs new/old REST APis.
On the Integration Guide page:
https://developer.yodlee.com/API_Resources/Integration_Guide
there is a note saying:
Yodlee Account Verification APIs use an earlier version of our API platform. Even though these APIs support standard REST and SOAP formats, the data model is different.
Can someone confirm the mess about the IAV documentation on the site and provide some guidance as to which APIs to use for IAV and which section of the site is current for IAV?
Basically IAV is used for real time user account verification.
For verification Yodlee provides two services: Data Service and Matching Service.
Data service – Yodlee uses the credentials provided by the consumer to log in to the specified bank website and returns all verification information found for the accounts at that site. The Yodlee customer then performs the verification by using their own rules.
Matching service – The account matching is done at Yodlee’s end based on Yodlee’s own matching algorithm.
REST IAV API flow: https://developer.yodlee.com/Account_Verification/API_Flow
I am trying to build a process to consume history api of Uber to display details of the users trips on one of my webpage. Has anyone done this?
I see that api definition on the UBER site
https://developer.uber.com/docs/rides/api/v12-history
However this does not provide how to provide the driver id? How can i get to the history of one particular driver?
All i need is trip details for every driver - assuming the driver id is available.
Any request sample will actually help.
Uber currently does not have API endpoints that provide information about driver activity. This is something we are considering, but at this time we do not have any public plans for a release.
Thanks for your interest in the Uber API. Follow #Uber_API and visit devblog.uber.com for updates and announcements.
I just wanted to know if I can use the REST API with an Italian account. I couldn't find any information about.
Thanks.
You can use REST api with an italian account, the link posted by KevinG does not state that you cannot.
I used it last year to implement Expresscheckout and it was working. Be sure to check if you need to be PCI or PCI-DSS compliant.
For more information you care read this faq https://developer.paypal.com/docs/faq/#non-US-dev
You can use REST API from Italy and you have a full access to all features in your sandbox account. In live account you have some limitations (no Direct credit cards processing!).
more info here (login in your developer account first): https://developer.paypal.com/developer/accountStatus
Currently the REST API is not available in Italy. This link will take you the the most current information regarding the REST API and supported countries:
https://developer.paypal.com/docs/integration/direct/rest_api_payment_country_currency_support/#direct-credit-card-payments
PayPal has recently released a new API which should replace the old API. The new API is based on a REST approach.
As fare as I can see there is no option to define a callback URL. In the old API the parameter was 'notify_url'. I use the following documentation:
https://developer.paypal.com/webapps/developer/docs/api/#create-a-payment
Is there a parameter in the new REST API which allows to define a notification URL?
Unfortunately, the REST API is still pretty far behind the classic API's with all of the features they provide. To my knowledge, notify_url/NOTIFYURL simply aren't included in the REST API yet.
That said, if you have IPN configured in your PayPal account profile the REST API calls should still trigger them. It's just that you can't override the value there with a custom one using notify like you're talking about.
The classic API's aren't going away, though. You can still use them just fine.