Lightsprint · Authentication Profile

Lightsprint Authentication

Authentication

Lightsprint secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyDeveloper ToolsArtificial IntelligenceAgentsSoftware DevelopmentProject ManagementCode GenerationTeam Collaboration
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

LightsprintOAuth2Api oauth2
· flows: authorizationCode

Source

Authentication Profile

lightsprint-authentication.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://github.com/SprintsAI/n8n-nodes-lightsprint/blob/main/credentials/LightsprintOAuth2Api.credentials.ts
notes: >-
  Lightsprint publishes no OpenAPI document, so this profile was NOT derived from a
  spec. It is captured from the provider's own published OAuth 2.0 credential
  definition in the first-party n8n community node, corroborated by the on-demand
  browser OAuth flow described in the Claude Code plugin README. Values are recorded
  verbatim from those sources.
docs: https://github.com/SprintsAI/n8n-nodes-lightsprint
summary:
  types: [oauth2]
  api_key_in: []
  oauth2_flows: [authorizationCode]
  token_placement: header
  token_refresh: automatic (CLI refreshes saved tokens)
schemes:
- name: LightsprintOAuth2Api
  type: oauth2
  display_name: Lightsprint OAuth2 API
  flows:
  - flow: authorizationCode
    authorizationUrl: https://lightsprint.ai/oauth/authorize
    tokenUrl: https://lightsprint.ai/oauth/token
    scope_count: 7
    scopes_artifact: scopes/lightsprint-scopes.yml
  sources:
  - https://github.com/SprintsAI/n8n-nodes-lightsprint/blob/main/credentials/LightsprintOAuth2Api.credentials.ts
verification:
  endpoint: GET /api/repo-key/info
  base_url: https://lightsprint.ai
  purpose: credential test — resolves the caller's repo/workspace id from the access
    token
tenancy:
  unit: workspace
  note: >-
    An access token is bound to one Lightsprint workspace; the repo id is resolved
    from the token via /api/repo-key/info rather than being passed by the client.
gaps:
- No public, human-readable authentication documentation page was found on
  lightsprint.ai — the auth contract is only discoverable from the published client
  source. No API-key alternative, no OIDC discovery document, no mutualTLS.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/lightsprint-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.