Arctic Wolf Networks · OAuth Scopes

Arctic Wolf Networks OAuth Scopes

OAuth 2.0 searched

Arctic Wolf Networks publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Arctic Wolf Networks API on a user’s behalf.

Tokens are issued from https://api-admin.cylance.com/public/v2/{region_code}/auth.

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.

CompanyCybersecuritySecurity OperationsManaged Detection and ResponseEndpoint SecurityThreat DetectionIncident Response
Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://api-admin.cylance.com/public/v2/{region_code}/auth
Flows
clientCredentials

Scopes (1)

ScopeDescriptionFlows
api The single scope requested on the client-credentials token request (scope=api); grants access to the Aurora Multi-Tenant / Endpoint Defense API resource surface for the authorized partner application. clientCredentials

Source

OAuth Scopes

arctic-wolf-networks-scopes.yml Raw ↑
generated: '2026-07-18'
method: searched
source: https://docs.arcticwolf.com/en/developer-and-oem/aurora-multi-tenant-api/aurora-multi-tenant-api/getting-started
docs: https://docs.arcticwolf.com/en/developer-and-oem/aurora-multi-tenant-api/aurora-multi-tenant-api
schemes:
- name: AuroraMultiTenantOAuth
  flows:
  - flow: clientCredentials
    tokenUrl: https://api-admin.cylance.com/public/v2/{region_code}/auth
scopes:
- scope: api
  description: >-
    The single scope requested on the client-credentials token request
    (scope=api); grants access to the Aurora Multi-Tenant / Endpoint Defense
    API resource surface for the authorized partner application.
  flows: [clientCredentials]
  sources: [docs.arcticwolf.com]
notes: >-
  Arctic Wolf's Aurora API documents a coarse-grained single-scope (api) OAuth
  client-credentials model rather than fine-grained per-resource scopes;
  authorization is scoped by the partner application's provisioned tenants.