Zayo Group Holdings OAuth Scopes

OAuth 2.0 searched

Zayo Group Holdings 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 Zayo Group Holdings API on a user’s behalf.

Tokens are issued from https://auth.api.zayo.com/oauth/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.

FiberNetworkInfrastructure

Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.api.zayo.com/oauth/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
openid	Standard OpenID Connect scope; the only scope value Zayo's docs instruct clients to include in the client_credentials token request. Zayo does not publish granular per-API permission scopes.

📄 Provider scope reference: https://developer.zayo.com/docs/getting-started

Source

OAuth Scopes

generated: '2026-07-11'
method: searched
source: openapi/zayo-group-openapi.yml
docs: https://developer.zayo.com/docs/getting-started
note: >-
  Zayo APIs use OAuth 2.0 client_credentials only; the Getting Started docs
  show a single standard `openid` scope in the token request and publish no
  granular permission scopes — access is governed by the issued client
  credentials (https://developer.zayo.com/docs/getting-started).
schemes:
- name: oauth2ClientCredentials
  source: openapi/zayo-group-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.api.zayo.com/oauth/token
  description: |-
    OAuth 2.0 Client Credentials grant. Exchange client_id / client_secret at
    the authorization server token endpoint for a short-lived bearer token
    (tokens expire hourly).
scopes:
- scope: openid
  description: >-
    Standard OpenID Connect scope; the only scope value Zayo's docs instruct
    clients to include in the client_credentials token request. Zayo does not
    publish granular per-API permission scopes.
  sources:
  - https://developer.zayo.com/docs/getting-started

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/zayo-group-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 email required.

GitHub Google LinkedIn

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