All geek questions in one place

Uber API v1.2 / get / pricing / price - does it support surge_multiplier or not?

Uber API v1.2 GET /estimates/price documentation contains ambiguity in defining surge_multiplier support: it is declared as one of the response parameters , but is not presented in the example response

Additionally, I checked the answer and comments on a similar Question and found there mutually exclusive information: "The pulse multiplier should not be returned to v1.2." against a response with an example response containing surge_multiplier

so what is the actual and expected behavior for this endpoint?

+5
source share
1 answer

Associated with the GET / Evaluation / Price endpoint specified in the Uber documentation:

When a surge is active for a particular product, its surge_multiplier will be greater than 1, but the price estimate already affects this factor.

The documentation also states that it is possible to get "surge_multiplier":

surge_multiplier float The expected surge factor. The flash is active if surge_multiplier is greater than 1. The evaluation score already affects the surge factor.

So if "surge_multiplier" does not return, it is always considered to be 1. If "surge_multiplier" is greater than 1, this parameter should be displayed. But, in addition, if this parameter is displayed or not, if a surge appears on the product, then the price estimate is already evaluated in this multiplier.

+2
source

Source: https://habr.com/ru/post/1275346/

More articles:


All Articles