Getting Started with Zayo APIs

Download OpenAPI specification:Download

Zayo offers a suite of APIs to make doing business with Zayo easier. Whether you're validating network coverage, generating quotes, placing orders, or managing services and tickets, this guide will walk you through everything you need to get connected.

Prerequisites

Before making your first API call, you will need:

• API credentials — a client_id and client_secret issued by the Zayo API team. To request access, email zayoapi@zayo.com or use the Request Access form.
• An OAuth 2.0 client — Zayo APIs use OAuth 2.0 (Client Credentials grant). Most HTTP clients and API frameworks support this natively.

Authentication

All Zayo API endpoints require a Bearer token. Tokens are obtained from the Zayo authorization server and expire hourly.

Obtaining a token

Make a POST request to the token endpoint with your credentials:

curl -X POST https://auth.api.zayo.com/oauth/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET"

A successful response returns a JSON object containing your access token:

{
  "access_token": "eyJ...",
  "token_type": "Bearer",
  "expires_in": 3600
}

Using a token

Include the token in the Authorization header of every request:

curl https://api.test.zayo.com/services/location-management/v2/buildings/validation \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "buildings": [{ "address": "60 Hudson Street", "countryCode": "US" }] }'

note

Tokens expire after one hour. Your integration should handle 401 Unauthorized responses by re-requesting a token automatically.

API Overview

Zayo APIs are organized into three capability areas:

Area	APIs
Network Discovery	Building Validation, Locations, Cloud Service Providers
Quote & Order	Product Catalog, Quoting, Orders
Service Management	Service Inventory, Ticket Catalog, Ticketing, Maintenance Cases

See the API Catalog for a full listing, or jump directly into the API Reference for endpoint-level documentation.

Versioning

• Major version upgrades happen no more than once per year.
• The previous major version is supported for a full year after a new major version is released, giving your teams time to upgrade.

Error Handling

Zayo APIs return standard HTTP status codes:

Range	Meaning
2xx	Request successfully received, understood, and accepted
3xx	Redirect — further action required to complete the request
4xx	Client error — bad syntax or request cannot be fulfilled
5xx	Server error — the server failed to fulfill a valid request

Getting Help

• Email: zayoapi@zayo.com for credentials, feature requests, or general questions
• Help Center: visit the FAQ for answers to common integration questions
• Request Access: use the Request Access form to get started