Code 42 · Authentication Profile

Code 42 Authentication

Authentication

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

CompanySecurityInsider Risk ManagementData Loss PreventionData SecurityEndpoint SecurityCybersecuritySaaS
Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

apiClientOAuth oauth2

Source

Authentication Profile

code-42-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://developer.code42.com/ + Code42 API clients docs
docs: https://developer.code42.com/
summary:
  types:
  - oauth2
  oauth2_flows:
  - clientCredentials
  token_lifetime_seconds: 900
  token_type: bearer
schemes:
- name: apiClientOAuth
  type: oauth2
  flow: clientCredentials
  description: >-
    Code42 API clients are OAuth 2.0-compliant. You create an API client in the
    Code42 console, which issues a client ID, secret, and a tenant-specific base
    URL (shown only once). Exchange the client ID and secret for a short-lived
    bearer token, then send that token on every API request.
  token_endpoint: https://api.us.code42.com/v1/oauth
  token_request: >-
    curl -X POST -u '<ClientID>:<Secret>' -d "" https://api.us.code42.com/v1/oauth
  token_response_example: '{"access_token":"...","token_type":"bearer","expires_in":900}'
  request_header: 'Authorization: Bearer <access_token>'
  token_expires_in: 900
  notes: >-
    Tokens expire after 15 minutes (900s). The token endpoint host is
    region-specific (api.us.code42.com, api.us2.code42.com, api.gov.code42.com,
    and other regional gateways). Permissions are governed by the role assigned
    to the API client, not by OAuth scopes; no public scope reference is
    documented, so no scopes/ artifact is emitted.