Lyft

Name: Lyft API
Brand: Lyft
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting Directionsoauth216 EndpointsREST

For Agents

Quote Lyft ride costs and ETAs, request and cancel rides, update destinations, and pull receipts via the Lyft platform.

Quickstart

Get started with Lyft in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"lyft cost estimate"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Lyft API.

Generate cost estimates between two coordinates with /cost

Return pickup ETAs and available drivers nearby for a coordinate

Request a ride with POST /rides and cancel an active request with POST /rides/{id}/cancel

Update the destination of an in-progress ride with PUT /rides/{id}/destination

Rate the driver with PUT /rides/{id}/rating after the ride completes

GET STARTED

Start building with Lyft API

Explore with Jentic

View OpenAPI Document

Use for: I need to quote the cost of a Lyft from one address to another, Get the pickup ETA for a Lyft at a coordinate, Find available Lyft drivers near a coordinate, Request a Lyft for a user and pass the rides.request scope

Not supported: Does not handle food delivery, scooter rentals, or driver-side dispatch — use for Lyft passenger ride quoting, requesting, updating, and receipt retrieval only.

Jentic publishes the only available OpenAPI document for Lyft, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Lyft, keeping it validated and agent-ready. This is the Jentic-imported Lyft ridesharing API spec at the bare 'lyft' vendor slug, covering the same 16 endpoints as the canonical lyft.com import: cost estimates, ETAs, available drivers nearby, ride request and lifecycle, ride types, profile, and a sandbox for state simulation. Authentication uses OAuth 2.0 with client credentials for public endpoints and authorization code for user-scoped ride operations.

Use Cases

Patterns agents use Lyft API for, with concrete tasks.

★ Embedded Lyft booking inside a partner product

Travel and concierge apps embed Lyft booking by chaining /cost and /eta to quote, POST /rides to request, and PUT /rides/{id}/destination to update. The user authentication OAuth flow grants the rides.request scope, and POST /rides/{id}/cancel handles cancellation. This is the same surface as the canonical lyft.com import — use whichever slug your tooling has pinned.

Call GET /cost and GET /eta for the trip coordinates, then POST /rides to request the ride.

Receipt and history retrieval for expense reporting

Expense and travel-management tools pull a user's recent rides via GET /rides and the receipt for a specific ride via GET /rides/{id}/receipt with the rides.read scope. This automates expense report attachments rather than relying on screenshots from the consumer Lyft app.

List the last 10 rides via GET /rides and fetch the receipt for each via GET /rides/{id}/receipt.

QA via the Lyft sandbox

Engineering teams drive a fake ride through state transitions before integrating against production. PUT /sandbox/rides/{id} propagates the ride through statuses, /sandbox/primetime sets a preset surge, and /sandbox/ridetypes preset the available types. This covers the full lifecycle without spending money on real rides.

PUT /sandbox/rides/{id} to walk a sandbox ride through pending, accepted, arrived, and completed states.

Agent-driven ride orchestration via Jentic

An AI travel concierge needs to book and adjust Lyft rides without juggling two OAuth flows or memorising sandbox vs production split. Jentic stores both client-credentials and authorization-code tokens in MAXsystem and exposes each Lyft operation by intent so the agent can chain cost, ETA, request, and cancel calls.

Search Jentic for 'lyft cost estimate', execute it for the trip, then chain POST /rides to request the ride.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for lyft, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/cost

Cost estimates for a trip

GET

/eta

Pickup ETAs

POST

/rides

Request a Lyft

POST

/rides/{id}/cancel

Cancel an ongoing ride request

PUT

/rides/{id}/destination

Update the destination of a ride

GET

/rides/{id}/receipt

Get the receipt for a completed ride

PUT

/sandbox/rides/{id}

Propagate a sandbox ride through status transitions

GET

/cost

Cost estimates for a trip

GET

/eta

Pickup ETAs

POST

/rides

Request a Lyft

POST

/rides/{id}/cancel

Cancel an ongoing ride request

PUT

/rides/{id}/destination

Update the destination of a ride

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Lyft OAuth client secret is held encrypted in the Jentic MAXsystem vault. Jentic exchanges it at https://api.lyft.com/oauth/token for the right scope (public, profile, rides.read, or rides.request) per call, so the agent's context never holds the raw secret.

Intent-based discovery

Agents search by intent such as 'lyft cost estimate', 'request a lyft', or 'cancel ride', and Jentic returns the matching Lyft operation with its parameter schema for direct execution.

Time to first call

Direct Lyft integration: 2-4 days to handle two OAuth flows, scope selection, and ride lifecycle state transitions. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Lyft

Same Lyft ridesharing API exposed under the lyft.com vendor slug

Prefer lyft.com/main as the canonical slug for new integrations; this 'lyft/main' slug exists to support pre-existing imports.

Complementary

Google Calendar

Calendar API for scheduling around booked rides

Pair with Google Calendar so an agent can pre-book a Lyft for the user's next meeting based on calendar context.

FAQs

Specific to using Lyft API through Jentic.

Why is there no official OpenAPI spec for Lyft?

Lyft does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lyft via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Lyft API use?

The Lyft API uses OAuth 2.0 with two flows: client credentials at https://api.lyft.com/oauth/token for public endpoints (cost, ETA) under the 'public' scope, and authorization code for user operations under 'profile', 'rides.read', and 'rides.request'. Jentic stores the client secret in MAXsystem and exchanges tokens automatically per call.

Can I request a ride and update its destination mid-trip?

Yes. POST /rides creates the request and returns a ride ID. While active you can PUT /rides/{id}/destination to change the destination, POST /rides/{id}/cancel to cancel, or wait for completion and call GET /rides/{id}/receipt for the final receipt.

What are the rate limits for the Lyft API?

Specific rate limits are not declared in this OpenAPI spec. Plan for per-application limits set in the Lyft developer portal — design clients to back off on 429 responses and avoid tight polling on /eta or /drivers.

How do I get a cost estimate through Jentic?

Search Jentic for 'lyft cost estimate', load GET /cost, and execute it with the start and end latitude/longitude. Jentic exchanges the client-credentials token automatically.