Skip to main content
POST
Preview a blueprint update

Authorizations

Authorization
string
header
required

JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '

Path Parameters

blueprintId
string<uuid>
required

Blueprint ID

Body

application/json
name
string
required

Display name for the service

Example:

"my-postgres"

tag
string
required

Catalog tag identifying the target blueprint version

Example:

"aws/postgres/17/1.1.0"

icon
string<uri>
required

Icon URL for the service

Example:

"https://cdn.qovery.com/icons/postgresql.svg"

variables
object

RFC 7396 patch map keyed by variable name. Non-null value upserts the variable; null value removes it. Absent keys are left untouched. Omitting the field entirely is equivalent to an empty map — no variables are modified.

spec_overrides
object | null

JSON Merge Patch (RFC 7396) applied to the stored spec_overrides (see BlueprintSpecOverrides for the list of valid fields). A non-null field value upserts the override; a null value removes it. Pass null or omit the field entirely to leave all existing overrides unchanged.

Example:

Response

Preview accepted

preview_id
string
required

Identifier of the preview execution

Example:

"exec-abc-123"

service_type
enum<string>
required

Type of the underlying service backing this blueprint

Available options:
HELM,
TERRAFORM