Automate Lyft
HumDay reads Lyft’s own published API description and derives 16 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Lyft is
Drive your app to success with Lyft's API
API host: api.lyft.com
What HumDay can do in Lyft
8 documented operations change something in Lyft.
- POSTRequest a Lyft
/rides - PUTAdd the passenger's rating, feedback, and tip
/rides/{id}/rating - POSTCancel a ongoing requested ride
/rides/{id}/cancel - PUTUpdate the destination of the ride
/rides/{id}/destination - PUTPreset Prime Time percentage
/sandbox/primetime - PUTPreset types of rides for sandbox
/sandbox/ridetypes - PUTPropagate ride through ride status
/sandbox/rides/{id} - PUTDriver availability for processing ride request
/sandbox/ridetypes/{ride_type}
What HumDay can read from Lyft
These are the operations a schedule or a trigger can watch.
- GETList rides
/rides - GETThe user's general info
/profile - GETGet the ride detail of a given ride ID
/rides/{id} - GETPickup ETAs
/eta - GETCost estimates
/cost - GETAvailable drivers nearby
/drivers - GETTypes of rides
/ridetypes - GETGet the receipt of the rides.
/rides/{id}/receipt
How automating Lyft works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Lyft account.
- Grant access, then go live. You approve the specific Lyft operations it may use — and only those.
Popular Lyft integrations
Connect Lyft to the tools people pair it with most.
- Lyft and OData for namespace microsoft.graphintegration
- Lyft and Cloudflareintegration
- Lyft and NetBoxintegration
- Lyft and GitHubintegration
- Lyft and Mistintegration
- Lyft and Loket.nlintegration
- Lyft and Atlassian The Jira Cloud platformintegration
- Lyft and Magento B2Bintegration
- Lyft and Stripeintegration
- Lyft and Zuora Reference Billingintegration
- Lyft and bunqintegration
- Lyft and DocuSignintegration
Automate Lyft with these
- HERE Tracking205 operations
- Traccar61 operations
- eDRV57 operations
- uebermaps endpoints56 operations
- Google My Business50 operations
- Weatherbit Interactive Swagger UI Documentation47 operations
- Waterlinked The Water Linked Underwater GPS38 operations
- OpenAQ36 operations
- Enode28 operations
- Neutrinoapi Neutrino27 operations
- Staging Ecotaco .ecota.co27 operations
- Viator Documentation & Specification Merchant Partners27 operations
Categories
Questions about Lyft automation
- Can HumDay connect to Lyft?
- Yes. HumDay reads Lyft's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.
- Do I need to write code to automate Lyft?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Lyft account.
- What can HumDay do in Lyft?
- 8 of the 16 documented operations change something in Lyft, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Lyft account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Lyft is held behind that approval.
Where this came from
The operations above are read from a published API description for Lyft at api.lyft.com/v1/spec. Descriptions are the provider’s own words, not ours. Last published 2018-11-28.