Create a blueprint service and report the dispatch it started
Instantiates a blueprint from the service catalog into the given environment and returns the ids of the engine dispatch it started. Pass deploy=true to trigger an immediate deployment after creation.
Takes the same request as POST /environment//blueprint. That endpoint answers 201, which claims a service that does not exist yet: the dispatch creating the underlying Helm/Terraform service runs on a background executor after the transaction commits. This one always answers 202 and hands back deployment_id and execution_id, which GET /blueprint/ resolves.
Authorizations
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
Environment ID
Query Parameters
Trigger a deployment immediately after creation
Body
Display name for the service
"my-postgres"
Catalog tag identifying the blueprint version
"aws/postgres/17/1.0.1"
Icon URL for the service
"https://cdn.qovery.com/icons/postgresql.svg"
Variable overrides for the blueprint
Engine-level overrides applied on top of the blueprint manifest. Only fields whose corresponding manifest field is overridable: true are accepted; submitting a non-overridable field returns 422.
Terraform / OpenTofu blueprints
engine_version is required on create. The value must be one of the versions listed in spec.engine.terraform.allowedValues (or opentofu.allowedValues) in the manifest.
Helm blueprints
engine_version, credentials, and backend are ignored. Only timeout and the resource fields apply.
Response
Blueprint created and an engine dispatch accepted
Answer to a blueprint creation: the blueprint exists and an engine dispatch was started. The service it should materialize does not exist yet.
URL to the blueprint catalog entry
"aws/postgres/17/1.0.1"
Identifier of the dispatch started by this creation. Resolve its status with GET /blueprint/{blueprintId}, and match it against latest_deployment.id there to confirm that dispatch is this one rather than a later re-dispatch.
Engine execution identifier for this dispatch
"exec-abc-123"