Get the ride detail of a given ride ID in Lyft
A documented Lyft operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get the ride detail of a given ride ID
- GETReads data · User
api.lyft.com/rides/{id}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Lyft operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Lyft operations
- Request a LyftPOST · changes data
- Add the passenger's rating, feedback, and tipPUT · changes data
- Cancel a ongoing requested ridePOST · changes data
- Update the destination of the ridePUT · changes data
- Preset Prime Time percentagePUT · changes data
- Preset types of rides for sandboxPUT · changes data
- Propagate ride through ride statusPUT · changes data
- Driver availability for processing ride requestPUT · changes data
Questions
- Can HumDay get the ride detail of a given ride id in Lyft?
- Yes. This operation is published in Lyft's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Lyft account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Lyft.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Lyft account.
Where this came from
Read from a published API description for Lyft at api.lyft.com/v1/spec. The description above is the provider’s own wording, not ours. Last published 2018-11-28.