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, list ride types, and retrieve receipts via the Lyft platform.

Install Jentic One Beta

Connect the Lyft to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lyft, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lyft API.

Generate cost estimates between two coordinates with /cost

Return available drivers nearby and pickup ETAs 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

GET STARTED

Start building with Lyft API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Lyft API for, with concrete tasks.

★ In-app ride booking inside another product

Travel apps and concierge services embed Lyft ride booking by chaining /cost and /eta to quote the trip, POST /rides to request it, and PUT /rides/{id}/destination if the user changes their mind mid-trip. The user authentication OAuth flow grants the rides.request scope, and POST /rides/{id}/cancel covers cancellation. This avoids deep linking out to the Lyft consumer app for partner experiences.

Call GET /cost and GET /eta for the pickup and dropoff coordinates, then POST /rides to request the ride if the quote is accepted.

Sandbox-based simulation for QA

Engineering teams use the /sandbox endpoints to drive a fake Lyft trip through state transitions before integrating against the live API. PUT /sandbox/rides/{id} propagates a ride through statuses, /sandbox/primetime sets a preset surge percentage, and /sandbox/ridetypes preset the available types. This lets QA cover the full lifecycle without spending money on real rides.

PUT /sandbox/rides/{id} to advance a sandbox ride from 'pending' to 'arrived' so the integration UI can be tested end to end.

Receipt and history retrieval for expense tools

Expense tools and travel managers pull a user's past Lyft rides via GET /rides and the receipt for a specific ride via GET /rides/{id}/receipt to attach to expense reports. With the rides.read scope, this avoids manual screenshotting from the Lyft app and enables automated reconciliation.

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

Agent-driven ride orchestration via Jentic

An AI travel concierge needs to book and adjust Lyft rides without juggling two OAuth flows or memorising the sandbox vs production split. Jentic stores both the client-credentials and authorization-code tokens in MAXsystem, exposes each Lyft operation by intent, and lets the agent 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 — the lyft api exposes lyft's ridesharing primitives — cost estimates, etas, available drivers nearby, ride request and lifecycle, ride types, profile, and a sandbox for simulating ride status transitions and primetime.

METHOD

PATH

DESCRIPTION

GET

/cost

Cost estimates for a trip

GET

/eta

Pickup ETAs

GET

/drivers

Available drivers nearby

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

GET

/cost

Cost estimates for a trip

GET

/eta

Pickup ETAs

GET

/drivers

Available drivers nearby

POST

/rides

Request a Lyft

POST

/rides/{id}/cancel

Cancel an ongoing ride request

PUT

/rides/{id}/destination

Why 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

Companion Jentic-curated import of the same Lyft ridesharing API

Use this duplicate slug if you have already pinned to it; both expose the same 16 ridesharing endpoints.

Complementary

Google Calendar

Calendar API for scheduling around booked rides

Pair with Google Calendar so an agent can read upcoming meetings and pre-book a Lyft for the next trip.

FAQs

Specific to using Lyft API through Jentic.

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'. Through Jentic, the Lyft client secret is stored in MAXsystem and tokens are exchanged automatically per call.

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

Yes. POST /rides creates the ride request and returns a ride ID. While the ride is active you can PUT /rides/{id}/destination to change the destination, POST /rides/{id}/cancel to cancel it, 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 polling /eta or /drivers more aggressively than once per few seconds per coordinate.

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 and returns the estimated price range.

Is the Lyft sandbox useful before going live?

Yes. The /sandbox endpoints (PUT /sandbox/rides/{id}, /sandbox/primetime, /sandbox/ridetypes) let you advance a fake ride through statuses, set a preset primetime percentage, and preset ride types, so you can test the full integration without spending money.