# Qovery: Platform API Reference Blueprint Main Calls

## Blueprint Main Calls

- [Get the blueprint service catalog](https://www.qovery.com/docs/api-reference/blueprint-main-calls/get-the-blueprint-service-catalog.md): Retrieves the Qovery service catalog from the public GitHub repository (Qovery/service-catalog). The catalog lists all available blueprints that can be deployed.
- [Create a blueprint service in an environment](https://www.qovery.com/docs/api-reference/blueprint-main-calls/create-a-blueprint-service-in-an-environment.md): Instantiates a blueprint from the service catalog into the given environment. Pass `deploy=true` to trigger an immediate deployment after creation.
- [Create a blueprint service and report the dispatch it started](https://www.qovery.com/docs/api-reference/blueprint-main-calls/create-a-blueprint-service-and-report-the-dispatch-it-started.md): 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/{environmentId}/blueprint. That endpoint answers 201,…
- [Check if a blueprint service has an available update](https://www.qovery.com/docs/api-reference/blueprint-main-calls/check-if-a-blueprint-service-has-an-available-update.md): Returns the update availability for a deployed blueprint service, including the latest tag, and a diff of variables that are new, changed, or removed.
- [Preview a blueprint update](https://www.qovery.com/docs/api-reference/blueprint-main-calls/preview-a-blueprint-update.md): Dry-runs a blueprint update without persisting any changes. Returns a preview ID and the resolved service type. Both `variables` and `spec_overrides` follow RFC 7396 patch semantics.
- [Deploy (apply) the current blueprint spec](https://www.qovery.com/docs/api-reference/blueprint-main-calls/deploy-apply-the-current-blueprint-spec.md): Deploys the blueprint's currently saved settings to its service. Call this after saving changes with PATCH /blueprint/{blueprintId} (and, optionally, previewing them) to roll them out. No request body: it deploys whatever is currently saved on the blueprint.
- [Get a blueprint service and the status of its latest dispatch](https://www.qovery.com/docs/api-reference/blueprint-main-calls/get-a-blueprint-service-and-the-status-of-its-latest-dispatch.md): Returns the blueprint, the Helm/Terraform service its dispatch produced once that service exists, and the latest dispatch with its status and the engine's error message. This is the only way to learn that a dispatch failed. Success is pushed over the `/blueprint/service-created` websocket, but there…
- [Update a blueprint service](https://www.qovery.com/docs/api-reference/blueprint-main-calls/update-a-blueprint-service.md): Persists new values for a deployed blueprint service. Intended to be called after reviewing the diff returned by GET /blueprint/{blueprintId}/update. `variables` and `spec_overrides` follow JSON Merge Patch (RFC 7396) semantics: non-null value on a key upserts it, null value removes it, absent keys…

## OpenAPI Specs

- [openapi](/docs/api-reference/openapi.yaml)