generated: '2026-08-28'
method: searched
source: https://skykick.developer.azure-api.net/getstarted
docs: https://skykick.developer.azure-api.net/getstarted
api: SkyKick Partner Integration API
flow: clientCredentials
token_url: https://apis.cloudservices.connectwise.com/auth/token
note: >-
  These are the only scope values SkyKick publishes anonymously. The Get Started
  page states them verbatim as "Valid scopes: Partner, Distributor" in the body of
  the token request. There is no OpenAPI oauth2 securityScheme to derive a fuller
  list from, and no published scopes/permissions reference page, so this artifact
  records exactly the two values the provider documents and nothing more. Per-scope
  operation mapping requires authenticated access to the gated API reference.
scope_count: 2
scopes:
- name: Partner
  description: >-
    Requested by an MSP partner tenant calling the Partner Integration API on its
    own behalf. Named as the example value in the provider's sample token request.
  evidence: 'grant_type=client_credentials&scope=Partner'
- name: Distributor
  description: >-
    Requested by a distributor tenant. Listed by the provider alongside Partner as
    a valid scope value; the provider publishes no further description of what it
    grants.
  evidence: 'Valid scopes: Partner, Distributor'
gaps:
- No published scope-to-operation mapping.
- No published reference page enumerating fine-grained permissions.
- No /.well-known/oauth-authorization-server document (probed 2026-08-28, HTTP 404).