Deployments
Upgrade deployment
Upgrade a managed Core instance through Blnk Cloud.
POST
Use this endpoint to upgrade a managed Core to the latest version Cloud supports. The deployment must be
ACTIVE. See Managed instances to learn more.
Cloud starts a new runtime next to the current one, health-checks it, then cuts traffic over. Ledger data and the Core secret stay in place.
Cloud creates a new deployment_id and a new instance_id. After cutover, use those new ids. Any requests sent to the old instance_id would fail or return errors.
The response returns the new deployment_id on new_deployment. Get the new instance_id from Get deployment details once the successor is provisioned.
This endpoint upgrades managed instances only. For a connected (self-hosted) instance, follow Upgrade Blnk Core.
Authorization
Blnk Cloud APIs support any one of the following authentication methods. All of them work with yourCLOUD_API_KEY or OAUTH_ACCESS_TOKEN.
Pass X-blnk-key: CLOUD_API_KEY or X-blnk-key: OAUTH_ACCESS_TOKEN.
Path
string
required
Unique id of the deployment to upgrade (
deploy_...). Do not pass instance_id here.Body
The body is optional. Omit it, or send{}, to upgrade to the latest Core version Cloud supports.
boolean
Set to
true to run the upgrade even when the deployment is already on the latest version. Default is false. When false and the deployment is already current, Cloud returns upgrade_status: "skipped".Response
object
The successor deployment Cloud is bringing up. Same shape as Get deployment details. Use this
deployment_id for later Deployments API calls.string
The
deployment_id you passed in the path. Cloud marks it UPGRADING, then retires it after cutover.string
Core version the old deployment was running.
string
Core version Cloud is rolling out.
string
in_progress when Cloud accepted the upgrade. skipped when the deployment is already on the latest version and you did not send force: true.string
Human-readable status. Track progress with Get deployment details on
new_deployment.deployment_id.