How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zayo Ticket Catalog API

View available tickets and ticket details to use in the Ticketing API.

Zayo Ticket Catalog API is one of 8 APIs that Zayo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ticket Catalog. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.zayo.com.

2 operations 2 paths 5 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.zayo.com
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Zayo Ticket Catalog API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerToken). It supports OAuth 2.0 (OAuthClientCredentials) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • BearerToken — Bearer token authentication.
  • OAuthClientCredentials — OAuth 2.0 using the Client Credentials grant type.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Ticket Catalog 2

View available tickets and ticket details to use in the Ticketing API.

GET
/services/service-management/v1/ticket-catalog
Get ticket catalog
getTicketCatalog → 200400
GET
/services/service-management/v1/ticket-type-details/{ticketType}/{version}
Get ticket type details
getTicketTypeDetails 2 params → 200400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are accessRequestTicketDetails (3 properties), customerServiceTicketDetails (2 properties), 400Response (2 properties), technicalSupportTicketDetails (2 properties). Each schema is shown below with its type and property counts.

billingTicketDetails
object
2 properties
technicalSupportTicketDetails
object
2 properties
accessRequestTicketDetails
object
3 properties
400Response
object
Bad Request
2 properties
customerServiceTicketDetails
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zayo-ticket-catalog-api-openapi.yml Raw ↑

Other APIs Zayo publishes across the network.

Zayo Maintenance Cases API
Zayo Network Discovery API
Zayo Order API
Zayo Product Catalog API
Zayo Quote API
Zayo Service Inventory API
Zayo Ticketing API
Where this information came from

This is an independent, third-party profile of Zayo Ticket Catalog API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.