/requests endpoint response doesn't match documentation

0
votes

I'm looking at the response for a request to /v1/requests/{request_id} but it doesn't match what is described in the documentation. In particular, I was hoping to get start lat/lng and end/lat among other information, but it seems like none of that is being returned. Is this a bug?

Thanks

1
uber-api
What exactly is being returned? Did you consider the status of your trip? Based on the status, the response content will vary. – Alexander Graebe

1 Answers

0
votes

Without further details, my assumption is that you are looking at a trip that is not ongoing. As you can find in the documentation, the pickup and destination fields are populated only when a trip is active.

If that is not helpful, please provide the HTTP request details (e.g. cURL), HTTP response payload and some details about the trips status to help us help you solve this issue.