Lilt · OAuth Scopes

Lilt OAuth Scopes

OAuth 2.0 searched

Lilt publishes 4 OAuth 2.0 scopes via the authorizationCode, deviceCode, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Lilt API on a user’s behalf.

Tokens are issued from https://blissful-celebration-62.authkit.app/oauth2/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.

CompanyAiTranslationLocalizationMachine TranslationLanguageContentTranslation MemoryAgents

Scopes: 4 Flows: authorizationCode, deviceCode, refreshToken Method: searched

OAuth endpoints

Authorization URL
https://blissful-celebration-62.authkit.app/oauth2/authorize

Token URL
https://blissful-celebration-62.authkit.app/oauth2/token

Flows
authorizationCodedeviceCoderefreshToken

Scopes (4)

Scope	Description	Flows
openid	OIDC — issue an ID token identifying the LILT MCP app user.	authorizationCode
profile	OIDC — access the user's basic profile claims.	authorizationCode
email	OIDC — access the user's email address claim.	authorizationCode
offline_access	Issue a refresh token so the MCP host can act without re-prompting.	authorizationCode, refreshToken

📄 Provider scope reference: https://support.lilt.com/kb/LILT-mcp

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: https://mcp.lilt.com/.well-known/oauth-authorization-server
docs: https://support.lilt.com/kb/LILT-mcp
description: >-
  The LILT REST API at api.lilt.com does NOT use OAuth — it authenticates with
  an organization API key over HTTP Basic (or a `key` query parameter), so it
  has no scope surface (see authentication/lilt-authentication.yml). The OAuth
  surface documented here belongs to LILT's hosted remote MCP server at
  mcp.lilt.com, whose RFC 8414 authorization-server metadata was fetched live.
  Authorization is delegated to WorkOS AuthKit; the advertised scopes are the
  standard OIDC set, so LILT does not expose per-capability translation scopes —
  tool-level authorization is enforced by the MCP server, not by scope.
applies_to: LILT MCP server (https://mcp.lilt.com/mcp)
schemes:
- name: MCPOAuth
  type: oauth2
  source: well-known/lilt-mcp-oauth-authorization-server.json
  issuer: https://blissful-celebration-62.authkit.app
  dynamic_client_registration: https://blissful-celebration-62.authkit.app/oauth2/register
  jwks_uri: https://blissful-celebration-62.authkit.app/oauth2/jwks
  introspection_endpoint: https://blissful-celebration-62.authkit.app/oauth2/introspection
  code_challenge_methods_supported: [S256]
  token_endpoint_auth_methods_supported: [none, client_secret_post, client_secret_basic]
  flows:
  - flow: authorizationCode
    authorizationUrl: https://blissful-celebration-62.authkit.app/oauth2/authorize
    tokenUrl: https://blissful-celebration-62.authkit.app/oauth2/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://blissful-celebration-62.authkit.app/oauth2/device_authorization
    tokenUrl: https://blissful-celebration-62.authkit.app/oauth2/token
  - flow: refreshToken
    tokenUrl: https://blissful-celebration-62.authkit.app/oauth2/token
scopes:
- scope: openid
  description: OIDC — issue an ID token identifying the LILT MCP app user.
  flows: [authorizationCode]
  sources: [well-known/lilt-mcp-oauth-authorization-server.json]
- scope: profile
  description: OIDC — access the user's basic profile claims.
  flows: [authorizationCode]
  sources: [well-known/lilt-mcp-oauth-authorization-server.json]
- scope: email
  description: OIDC — access the user's email address claim.
  flows: [authorizationCode]
  sources: [well-known/lilt-mcp-oauth-authorization-server.json]
- scope: offline_access
  description: Issue a refresh token so the MCP host can act without re-prompting.
  flows: [authorizationCode, refreshToken]
  sources: [well-known/lilt-mcp-oauth-authorization-server.json]
notes:
- >-
  No LILT-specific (translation, job, model) scopes are advertised. Agent
  capability is bounded by the MCP tool set in mcp/lilt-mcp.yml, not by scope.
- >-
  MCP app accounts at mcp.lilt.com are separate from lilt.com platform accounts.