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

Yugabyte GFlags Validation APIs API

The GFlags Validation APIs API from Yugabyte — 3 operation(s) for gflags validation apis.

Yugabyte GFlags Validation APIs API is one of 82 APIs that Yugabyte publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include GFlags Validation APIs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

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

Requests are made against a single base URL, /.

3 operations 3 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://cloud.yugabyte.com/api/public/v1
Authentication
API Key
Contact
https://docs.yugabyte.com
Terms of Service
Resource Areas
1

Authentication & Security 1

Yugabyte GFlags Validation APIs API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-AUTH-YW-API-TOKEN (apiKeyAuth).

  • apiKeyAuth — API token passed as header

Paths & Operations 3

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

GFlags Validation APIs 3
GET
/api/v1/metadata/version/{version}/gflag
Get gflag metadata
getGFlagMetadata 3 params → 200
GET
/api/v1/metadata/version/{version}/list_gflags
List all gflags for a release
listGFlags 5 params → 200
POST
/api/v1/metadata/version/{version}/validate_gflags
Validate gflags
validateGFlags 2 params body → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are GFlagDetails (9 properties), GFlagsValidationResponse (3 properties), GFlagsValidationRequest (3 properties), GFlagValidationDetails (2 properties). Each schema is shown below with its type and property counts.

GFlagDetails
object
9 properties
GFlagsValidationRequest
object
3 properties
GFlagsValidationResponse
object
3 properties
GFlagsValidationFormData
object
1 property
GFlagValidationDetails
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yugabyte-gflags-validation-apis-api-openapi.yml Raw ↑

Other APIs Yugabyte publishes across the network.

YugabyteDB Aeon REST API
Yugabyte Backup Info API
Yugabyte Cluster API
Yugabyte Cluster Info API
Yugabyte Pitr Info API
Yugabyte Restore Info API
Yugabyte Voyager Info API
Yugabyte Voyager Metrics API
Yugabyte Xcluster Metrics API
Yugabyte Xcluster Namespace Details API
Yugabyte Access Keys API
Yugabyte Accounts API
Where this information came from

This is an independent, third-party profile of Yugabyte GFlags Validation APIs 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.