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

Google Cloud CDN BackendServices API

Manage CDN-enabled backend services

Google Cloud CDN BackendServices API is one of 3 APIs that Google Cloud CDN publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include BackendServices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, and 1 JSON Schema.

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

Requests are made against a single base URL, https://compute.googleapis.com/compute/v1.

5 operations 2 paths 2 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://compute.googleapis.com
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

Google Cloud CDN BackendServices API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 5

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

BackendServices 5

Manage CDN-enabled backend services

GET
/projects/{project}/global/backendServices
Google Cloud CDN List Backend Services
listBackendServices 1 param → 200
POST
/projects/{project}/global/backendServices
Google Cloud CDN Create Backend Service
insertBackendService 1 param body → 200
GET
/projects/{project}/global/backendServices/{backendService}
Google Cloud CDN Get Backend Service
getBackendService 2 params → 200
PATCH
/projects/{project}/global/backendServices/{backendService}
Google Cloud CDN Update Backend Service
patchBackendService 2 params body → 200
DELETE
/projects/{project}/global/backendServices/{backendService}
Google Cloud CDN Delete Backend Service
deleteBackendService 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are BackendService (10 properties), Operation (7 properties). Each schema is shown below with its type and property counts.

BackendService
object
10 properties
Operation
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-cloud-cdn-backendservices-api-openapi.yml Raw ↑

Other APIs Google Cloud CDN publishes across the network.

Google Cloud CDN CacheInvalidation API
Google Cloud CDN UrlMaps API
Where this information came from

This is an independent, third-party profile of Google Cloud CDN BackendServices 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.