Get basic build, version, and cluster information.
::: In Serverless, version.number always reports the next target Elasticsearch release version at the time of the request. Serverless does not track to a traditional release versioning model; it is continuously updated. The version number is provided to maintain compatibility with existing clients, but it is not meaningful for assessing feature availability. Clients should detect a Serverless environment by checking for build_flavor: serverless.
Version information for the Elasticsearch cluster. In Serverless, version.number always reports the next target Elasticsearch release version at the time of the request, not an actual deployed version. The version number is provided to maintain client compatibility but is not meaningful for assessing feature availability. Use build_flavor: serverless to detect a Serverless environment.
build_dateuniononeOfrequired
The Elasticsearch Git commit's date.
One of:stringornumber
build_flavorstringrequired
The build flavor. For example, default.
build_hashstringrequired
The Elasticsearch Git commit's SHA hash.
build_snapshotbooleanrequired
Indicates whether the Elasticsearch build was a snapshot.
build_typestringrequired
The build type that corresponds to how Elasticsearch was installed.
For example, docker, rpm, or tar.
lucene_versionstringrequired
The version number of Elasticsearch's underlying Lucene software.
minimum_index_compatibility_versionstringrequired
The minimum index version with which the responding node can read from disk.
minimum_wire_compatibility_versionstringrequired
The minimum node version with which the responding node can communicate.
Also the minimum version from which you can perform a rolling upgrade.
numberstringrequired
The Elasticsearch version number.
Serverless environments are versionless and automatically upgraded, so this value can be safely ignored.