---
title: "Redeploy with Updated Secrets"
method: POST
path: "/branches/{branch_id}/redeploy"
tags: ["Branches"]
---

# Redeploy with Updated Secrets

`POST /branches/{branch_id}/redeploy`

Redeploy a branch with the current secrets from the EnvVar table.

    Creates a new Version with:
    - Same image as current version
    - Fresh secrets_snapshot from current EnvVars

    Use this after updating secrets to apply them to a running branch.

## Path parameters

- `branch_id` string, required

## Response `200`

Successful Response

- RedeployResponse — Response from a redeploy operation.
  - `branch_id` string, required — Branch ID
  - `message` string, required — Human-readable status message
  - `version_id` string, required — New version ID created for redeploy
  - `version_status` 'DEPLOYING' | 'ACTIVE' | 'FAILED' | 'UNHEALTHY' | 'DRAINING' | 'RETIRED' | 'ROLLED_BACK', required — Status of a version in its lifecycle.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/terminaluse/apis/sb0-api.md) · [All operations](https://skmtc.net/terminaluse/apis/sb0-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/terminaluse/sb0-api/versions/f24a474dc415/schema)