How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

lyft Rides API

Endpoints for requesting, tracking, canceling, and managing Lyft rides on behalf of an authenticated user.

lyft Rides API is one of 7 APIs that Lyft publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rides. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 6 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.lyft.com/v1.

7 operations 6 paths 11 schemas 3 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.lyft.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

lyft Rides API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 access token obtained through the client credentials flow for the organization's concierge API client.

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 3 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Rides 7

Endpoints for requesting, tracking, canceling, and managing Lyft rides on behalf of an authenticated user.

GET
/rides
List rides
listRides 3 params → 200400401
POST
/rides
Request a ride
createRide body → 200400401404
GET
/rides/{id}
Get ride detail
getRide 1 param → 200401404
POST
/rides/{id}/cancel
Cancel a ride
cancelRide 1 param body → 204400401404
PUT
/rides/{id}/destination
Update ride destination
updateRideDestination 1 param body → 200400401404
PUT
/rides/{id}/rating
Rate a ride
rateRide 1 param body → 200400401404
GET
/rides/{id}/receipt
Get ride receipt
getRideReceipt 1 param → 200401404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are RideDetail (12 properties), Vehicle (7 properties), RideReceipt (5 properties), Driver (4 properties). Each schema is shown below with its type and property counts.

RideRatingRequest
object
Request body for rating a completed ride.
3 properties 1 required
RideTypeEnum
string
Identifier for the type of Lyft ride.
CreateRideRequest
object
Request body for creating a new Lyft ride.
4 properties 2 required
Driver
object
Information about the driver assigned to a ride.
4 properties
RideDetail
object
Detailed information about a Lyft ride including its status, route, driver, and vehicle information.
12 properties
LineItem
object
A single line item on a ride receipt representing a specific charge or credit.
3 properties
Charge
object
A payment charge applied to a ride.
3 properties
RideReceipt
object
Receipt for a completed ride, including fare breakdown and total charges.
5 properties
Location
object
A geographic location with optional address information.
3 properties
Price
object
Price information for a ride, including the total amount and currency.
3 properties
Vehicle
object
Information about the vehicle assigned to a ride.
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lyft-rides-api-openapi.yml Raw ↑

Other APIs Lyft publishes across the network.

lyft Concierge Rides API
lyft Cost Estimates API
lyft Drivers API
lyft ETA API
lyft Profile API
lyft Ride Types API
Where this information came from

This is an independent, third-party profile of lyft Rides API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.