Larridin · Authentication Profile

Larridin Authentication

Authentication

Larridin secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, refreshToken, and deviceCode flow(s).

CompanyArtificial IntelligenceAI AdoptionAI GovernanceAnalyticsDeveloper ProductivityDeveloper IntelligenceWorkflow IntelligenceEnterprise SoftwareObservability
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode, refreshToken, deviceCode API key in: header

Security Schemes

companyApiKey apiKey
· in: header (x-company-api-key)
larridinOAuth oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: openapi/larridin-scout-openapi.yml
docs: https://docs.larridin.com/api/scout-api-v1-reference
notes: >-
  Larridin runs two distinct authentication models. The Scout REST API v1 uses a company API key in the
  x-company-api-key header and requires the ANALYTICS scope. The beta MCP server at /mcp/larridin uses
  OAuth 2.0 with an authorization server at https://login.larridin.com, discovered via RFC 8414
  authorization-server metadata and RFC 9728 protected-resource metadata. End-user access to the
  Larridin application itself is documented as SSO.
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  - refreshToken
  - deviceCode
schemes:
- name: companyApiKey
  type: apiKey
  in: header
  parameter: x-company-api-key
  description: Company API key. The ANALYTICS scope is required for Scout API v1 endpoints.
  applies_to: Scout API v1 (https://scout-api.larridin.com/api/v1)
  docs: https://docs.larridin.com/api/scout-api-v1-reference
  sources:
  - openapi/larridin-scout-openapi.yml
- name: larridinOAuth
  type: oauth2
  description: >-
    OAuth 2.0 authorization used by the Larridin MCP server. Compatible MCP clients discover the
    authorization-server and protected-resource metadata and prompt the user to sign in.
  applies_to: Larridin MCP server (https://app.larridin.com/mcp/larridin)
  issuer: https://login.larridin.com
  authorization_endpoint: https://login.larridin.com/oauth2/authorize
  token_endpoint: https://login.larridin.com/oauth2/token
  jwks_uri: https://login.larridin.com/oauth2/jwks
  registration_endpoint: https://login.larridin.com/oauth2/register
  introspection_endpoint: https://login.larridin.com/oauth2/introspection
  device_authorization_endpoint: https://login.larridin.com/oauth2/device_authorization
  grant_types:
  - authorization_code
  - refresh_token
  - 'urn:ietf:params:oauth:grant-type:device_code'
  pkce_methods:
  - S256
  token_endpoint_auth_methods:
  - none
  - client_secret_post
  - client_secret_basic
  dynamic_client_registration: true
  bearer_methods_supported:
  - header
  docs: https://docs.larridin.com/api/mcp
  sources:
  - well-known/larridin-oauth-authorization-server.json
  - well-known/larridin-oauth-protected-resource.json
sso:
  documented: true
  docs: https://docs.larridin.com/setup/sso