Lyft · OAuth Scopes

Lyft OAuth Scopes

OAuth 2.0 probed

Lyft publishes 47 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Lyft API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

TransportationMobilityRide HailingMicromobilityBike ShareScootersGBFSLogisticsTravel
Scopes: 47 Flows: Method: probed

Scopes (47)

ScopeDescriptionFlows
autonomouspartners.set
driver.details.address
driver.details.basic
driver.details.license
drivers.tracking.read
enterprise.support_tickets.create
external_supply_integrator
lb.ride_costs.get
lb.ride_receipts.get
lb.rides.cancel
lb.rides.dispatch
lb.rides.update
loyalty_tier
lus_partnership.account_management
lyft_enterprise.admin_access
lyft_rewards.usage
lyft_rider_mcp.read
memberships.updates_subscribe
offline
openid
privileged.admin
privileged.b2b_payouts.boomi_partner_records
privileged.driver.tax.summary
privileged.enterprise.dell_boomi
privileged.enterprise.invoices
privileged.enterprise.ride_program
privileged.mobility.rides
privileged.price.upfront
privileged.rides.additional_fields.drivers_license
privileged.rides.dispatch
privileged.wav_dispatch
profile
profile.email
profile.phone
public
rides.active_ride
rides.read
rides.request
rides.subscribe_all
rides.subscribe_ride_receipt
rides.subscribe_ride_request
routes.read
scopedurl
tapi.atms.webhook
transportation_api.trip_insights
transportation_api.trips
users.create

Source

OAuth Scopes

Raw ↑
specification: API Commons OAuth Scopes
specificationVersion: '0.1'
provider: lyft
providerId: lyft
generated: '2026-09-17'
method: probed
source: https://api.lyft.com/.well-known/oauth-authorization-server
description: 'The complete OAuth 2.0 scope vocabulary Lyft publishes for api.lyft.com, read verbatim from
  the provider''s own RFC 8414 authorization-server metadata. Lyft''s developer portal is login-gated,
  so this anonymous discovery document is the only public source for the scope vocabulary; no scope reference
  page is publicly readable and Lyft publishes no human-readable description for any individual scope,
  so none is recorded here. The family: grouping is our own, derived from the scope prefix.'
docs: null
docs_note: 'No publicly readable scope/permission reference page: https://www.lyft.com/developers 302s
  to https://account.lyft.com/auth/email.'
issuer: https://api.lyft.com
authorization_endpoint: https://api.lyft.com/oauth/authorize
token_endpoint: https://api.lyft.com/oauth/token
grant_types_supported:
- authorization_code
- client_credentials
- refresh_token
code_challenge_methods_supported:
- S256
token_endpoint_auth_methods_supported:
- client_secret_basic
- none
scope_count: 47
scopes:
- scope: autonomouspartners.set
  family: other
- scope: driver.details.address
  family: driver
- scope: driver.details.basic
  family: driver
- scope: driver.details.license
  family: driver
- scope: drivers.tracking.read
  family: driver
- scope: enterprise.support_tickets.create
  family: enterprise
- scope: external_supply_integrator
  family: other
- scope: lb.ride_costs.get
  family: lyft-business
- scope: lb.ride_receipts.get
  family: lyft-business
- scope: lb.rides.cancel
  family: lyft-business
- scope: lb.rides.dispatch
  family: lyft-business
- scope: lb.rides.update
  family: lyft-business
- scope: loyalty_tier
  family: openid-connect-and-core
- scope: lus_partnership.account_management
  family: other
- scope: lyft_enterprise.admin_access
  family: enterprise
- scope: lyft_rewards.usage
  family: memberships-and-rewards
- scope: lyft_rider_mcp.read
  family: agent/mcp
- scope: memberships.updates_subscribe
  family: memberships-and-rewards
- scope: offline
  family: openid-connect-and-core
- scope: openid
  family: openid-connect-and-core
- scope: privileged.admin
  family: privileged (partner-restricted)
- scope: privileged.b2b_payouts.boomi_partner_records
  family: privileged (partner-restricted)
- scope: privileged.driver.tax.summary
  family: privileged (partner-restricted)
- scope: privileged.enterprise.dell_boomi
  family: privileged (partner-restricted)
- scope: privileged.enterprise.invoices
  family: privileged (partner-restricted)
- scope: privileged.enterprise.ride_program
  family: privileged (partner-restricted)
- scope: privileged.mobility.rides
  family: privileged (partner-restricted)
- scope: privileged.price.upfront
  family: privileged (partner-restricted)
- scope: privileged.rides.additional_fields.drivers_license
  family: privileged (partner-restricted)
- scope: privileged.rides.dispatch
  family: privileged (partner-restricted)
- scope: privileged.wav_dispatch
  family: privileged (partner-restricted)
- scope: profile
  family: openid-connect-and-core
- scope: profile.email
  family: profile
- scope: profile.phone
  family: profile
- scope: public
  family: openid-connect-and-core
- scope: rides.active_ride
  family: rider-rides
- scope: rides.read
  family: rider-rides
- scope: rides.request
  family: rider-rides
- scope: rides.subscribe_all
  family: rider-rides
- scope: rides.subscribe_ride_receipt
  family: rider-rides
- scope: rides.subscribe_ride_request
  family: rider-rides
- scope: routes.read
  family: rider-rides
- scope: scopedurl
  family: openid-connect-and-core
- scope: tapi.atms.webhook
  family: transportation-api
- scope: transportation_api.trip_insights
  family: transportation-api
- scope: transportation_api.trips
  family: transportation-api
- scope: users.create
  family: other
notes:
- openid + profile + offline are present, but api.lyft.com serves no /.well-known/openid-configuration
  (404), so the OIDC discovery document is absent even though OIDC scopes are advertised.
- lyft_rider_mcp.read is an MCP-specific scope in the published vocabulary — first-party evidence that
  an MCP surface exists behind authentication. No anonymously reachable MCP endpoint was found (see mcp/lyft-mcp.yml).
- rides.subscribe_all, rides.subscribe_ride_request, rides.subscribe_ride_receipt, memberships.updates_subscribe
  and tapi.atms.webhook are subscription/webhook scopes (see asyncapi/lyft-webhooks.yml).
- The 18 operations in openapi/ are covered by a small part of this vocabulary; most scopes belong to
  Lyft Business, enterprise, driver and privileged partner surfaces that publish no public contract.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/lyft-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.