Daylight · Authentication Profile

Daylight Authentication

Authentication

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

CompanySecurityCybersecurityManaged Detection and ResponseMDRThreat DetectionIncident ResponseAgentic AISOCMCP
Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, clientCredentials, refreshToken API key in:

Security Schemes

daylight-api-oidc openIdConnect
daylight-docs-mcp-oauth oauth2

Source

Authentication Profile

daylight-authentication.yml Raw ↑
generated: '2026-07-18'
method: searched
source: >-
  https://api.daylight.ai/.well-known/oauth-protected-resource +
  https://auth.app.daylight.ai/v1/apps/Peuc12rtvwjSr4gXbIvmOHyv8UyFi29b/.well-known/openid-configuration +
  https://docs.daylight.ai/.well-known/oauth-authorization-server
summary:
  types: [oauth2, openIdConnect]
  bearer_methods: [header]
  oauth2_flows: [authorizationCode, clientCredentials, refreshToken]
  notes: >-
    No public API keys or docs auth page; the product API is OAuth2/OIDC only.
    Discovery metadata indicates a Stytch "Connected Apps" authorization server.
schemes:
- name: daylight-api-oidc
  type: openIdConnect
  applies_to: https://api.daylight.ai
  bearer_methods_supported: [header]
  scopes_supported: [openid]
  issuer: https://auth.app.daylight.ai/v1/apps/Peuc12rtvwjSr4gXbIvmOHyv8UyFi29b
  authorization_endpoint: https://auth.app.daylight.ai/oauth2/v1/apps/authorize
  token_endpoint: https://auth.app.daylight.ai/oauth2/v1/apps/token
  userinfo_endpoint: https://auth.app.daylight.ai/oauth2/v1/apps/userinfo
  revocation_endpoint: https://auth.app.daylight.ai/oauth2/v1/apps/revoke
  jwks_uri: https://auth.app.daylight.ai/Peuc12rtvwjSr4gXbIvmOHyv8UyFi29b/.well-known/jwks.json
  registration_endpoint: https://auth.app.daylight.ai/v1/mgmt/inboundapp/app/Peuc12rtvwjSr4gXbIvmOHyv8UyFi29b/register
  response_types_supported: [code]
  id_token_signing_alg_values_supported: [RS256]
  code_challenge_methods_supported: [S256]
  token_endpoint_auth_methods_supported: [none, client_secret_basic, client_secret_post]
  grant_types_supported:
  - authorization_code
  - refresh_token
  - client_credentials
  - urn:openid:params:grant-type:ciba
  - urn:ietf:params:oauth:grant-type:jwt-bearer
  - urn:ietf:params:oauth:grant-type:token-exchange
  dpop_signing_alg_values_supported: [RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512, EdDSA]
  claims_supported: [iss, aud, iat, exp, sub, name, email, email_verified, phone_number, phone_number_verified, picture, family_name, given_name]
- name: daylight-docs-mcp-oauth
  type: oauth2
  applies_to: https://docs.daylight.ai/mcp
  issuer: https://docs.daylight.ai/mcp/oauth
  authorization_endpoint: https://docs.daylight.ai/mcp/oauth/authorize
  token_endpoint: https://docs.daylight.ai/mcp/oauth/token
  registration_endpoint: https://docs.daylight.ai/mcp/oauth/register
  response_types_supported: [code]
  grant_types_supported: [authorization_code, client_credentials, refresh_token]
  token_endpoint_auth_methods_supported: [none, client_secret_post, client_secret_basic]
  code_challenge_methods_supported: [S256]
  scopes_supported: [mcp:search]