List the published engine versions.

GET

/v1/db/engine-versions

Code sample: Shell / cURL

curl --request GET \
  --url 'https://stratum.example.com/v1/db/engine-versions?engine=postgres' \
  --header 'Authorization: Bearer <token>'

• A Stratum cluster endpoint.

What the operator has published: for each major.minor an engine image exists in p-system-db and a launch template points at it. A customer picks one of these (or a bare major for its latest minor). Readable by any authenticated principal; imageId is filled for operators only.

Authorizations

• bearerAuth

Parameters

Query Parameters

engine

string

Allowed values: postgres

Responses

200

Engine versions.

Media typeapplication/json

object

items

required

Array<object>

What the operator has published: an engine image exists and a launch template in p-system-db points at it.

object

engine

required

string

version

required

16.4

string

family

required

postgres16

string

status

required

string

Allowed values: available deprecated

imageId

The engine image in p-system-db (operator view only; null for tenants).

string

nullable

publishedAt

string format: date-time

majorStatus

The major’s place in the catalog (as amended): current takes new instances; legacy keeps running what exists (modify, restore, minor upgrades, blue/green out of it) but refuses a new instance; next is the operator’s preview of the coming major built on demand and published so the recipe is proven, not offered.

string

Allowed values: current legacy next

supportedExtensions

The extension catalog. trusted: true means the master role creates it itself with CREATE EXTENSION; the rest are untrusted — the service creates them, and they are what an instance’s extensions accepts.

Array<object>

object

name

required

string

trusted

required

boolean

requiresPreload

The shared_preload_libraries entry the extension needs first.

string

description

string

Example

{
  "items": [
    {
      "status": "available",
      "majorStatus": "current"
    }
  ]
}