Cancel a ongoing requested ride in Lyft
A documented Lyft operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Cancel a ongoing requested ride
- POSTChanges data · User
api.lyft.com/rides/{id}/cancel
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. Because this one changes data, it cannot run until you have explicitly granted it.
Other Lyft operations
- Request a LyftPOST · changes data
- Add the passenger's rating, feedback, and tipPUT · 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
- The user's general infoGET · reads data
Questions
- Can HumDay cancel a ongoing requested ride 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.
- Will this change my Lyft data?
- Yes — this is a POST operation, so it changes something in Lyft. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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.