SkyKick · OAuth Scopes

SkyKick OAuth Scopes

OAuth 2.0 searched

SkyKick publishes 2 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the SkyKick API on a user’s behalf.

Tokens are issued from https://apis.cloudservices.connectwise.com/auth/token.

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.

CompanyBackupMigrationMicrosoft 365Managed Service ProvidersSaaS SecurityCloud AutomationData ProtectionAzure API Management

Scopes: 2 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://apis.cloudservices.connectwise.com/auth/token

Flows
clientCredentials

Scopes (2)

Scope	Description	Flows
Partner	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.
Distributor	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.

📄 Provider scope reference: https://skykick.developer.azure-api.net/getstarted

Source

OAuth Scopes

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).

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/skykick-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.