Lusha · OAuth Scopes

Lusha OAuth Scopes

OAuth 2.0 probed

Lusha publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Lusha API on a user’s behalf.

Tokens are issued from https://auth.lusha.com/oauth/token.

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.

Sales IntelligenceB2BEnrichmentContact DataProspectingIntentSignalsLookalikesWebhookMCP

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://auth.lusha.com/oauth-ui/authorize

Token URL
https://auth.lusha.com/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Full access to the Lusha MCP tool surface for the authenticated user — search, enrichment, prospecting, lookalikes, signals, recommendations and account usage. Credit-consuming tools are covered by the same scope as read-only filter tools.	authorizationCode

📄 Provider scope reference: https://docs.lusha.com/mcp-docs

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://mcp.lusha.com/.well-known/oauth-authorization-server
docs: https://docs.lusha.com/mcp-docs
description: >-
  The Lusha REST API has NO OAuth surface — it authenticates with a single
  `api_key` header and therefore has no scopes (derive-oauth-scopes.py over the
  OpenAPI correctly finds zero oauth2 schemes). OAuth exists only in front of the
  MCP server, and it advertises exactly one coarse scope, `mcp`, which grants a
  connected agent the whole published tool set. There is no read/write split, no
  per-product scope, and no per-tool consent surface.
applies_to: mcp
schemes:
- name: LushaMCPOAuth
  type: oauth2
  source: https://mcp.lusha.com/.well-known/oauth-protected-resource
  resource: https://mcp.lusha.com
  authorization_server: https://auth.lusha.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.lusha.com/oauth-ui/authorize
    tokenUrl: https://auth.lusha.com/oauth/token
    refreshUrl: https://auth.lusha.com/oauth/token
    revocationUrl: https://auth.lusha.com/oauth/revoke
    registrationUrl: https://auth.lusha.com/oauth/register
    pkce: S256
    token_endpoint_auth_methods: [client_secret_post, client_secret_basic]
  bearer_methods: [header]
scopes:
- scope: mcp
  description: >-
    Full access to the Lusha MCP tool surface for the authenticated user —
    search, enrichment, prospecting, lookalikes, signals, recommendations and
    account usage. Credit-consuming tools are covered by the same scope as
    read-only filter tools.
  flows: [authorizationCode]
  sources: [https://mcp.lusha.com/.well-known/oauth-authorization-server]
scope_count: 1
gaps:
- >-
    A single scope means an agent granted MCP access can spend credits (contact
    and company reveals at 1-5 credits per data point) with no narrower consent
    step. A read-only / filters-only scope would let an operator hand an agent
    discovery without spend.
x-evidence:
- url: https://mcp.lusha.com/.well-known/oauth-authorization-server
  http_status: 200
- url: https://mcp.lusha.com/.well-known/oauth-protected-resource
  http_status: 200
- url: https://auth.lusha.com/.well-known/oauth-protected-resource
  http_status: 200