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 Endpoints Services API

The Services API from Google Cloud Endpoints — 4 operation(s) for services.

Google Cloud Endpoints Services API is published by Google Cloud Endpoints on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Services. 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 8 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version v1.

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

8 operations 4 paths 7 schemas 1 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://servicemanagement.googleapis.com
Resource Areas
1

Paths & Operations 8

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

Services 8
GET
/v1/services
Google Cloud Endpoints List managed services
listServices 3 params → 200
POST
/v1/services
Google Cloud Endpoints Create a managed service
createService body → 200
GET
/v1/services/{serviceName}
Google Cloud Endpoints Get a managed service
getService 1 param → 200
DELETE
/v1/services/{serviceName}
Google Cloud Endpoints Delete a managed service
deleteService 1 param → 200
GET
/v1/services/{serviceName}/configs
Google Cloud Endpoints List service configurations
listServiceConfigs 1 param → 200
POST
/v1/services/{serviceName}/configs
Google Cloud Endpoints Create a service configuration
createServiceConfig 1 param body → 200
GET
/v1/services/{serviceName}/rollouts
Google Cloud Endpoints List service rollouts
listServiceRollouts 1 param → 200
POST
/v1/services/{serviceName}/rollouts
Google Cloud Endpoints Create a service rollout
createServiceRollout 1 param body → 200

Schemas 7

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

ServiceConfig
object
8 properties
ManagedService
object
2 properties
Operation
object
5 properties
ListServiceConfigsResponse
object
2 properties
ListServiceRolloutsResponse
object
2 properties
ListServicesResponse
object
2 properties
Rollout
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-cloud-endpoints-services-api-openapi.yml Raw ↑
Where this information came from

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