Create activate — POST /v1/projects/{slug}/releases/{release}/activate

Points the site at an existing release — the go-live, and equally the ROLLBACK.

POST /v1/projects/{slug}/releases/{release}/activate

Addresshttps://api.hanzo.ai/v1/projects/{slug}/releases/{release}/activate
MethodPOST
Operationpost_projects_by_slug_releases_by_release_activate
AuthAuthorization: Bearer $HANZO_API_KEY

Points the site at an existing release — the go-live, and equally the ROLLBACK.

Aim it at an older release and the site serves that one again: releases are immutable and retained to the retention depth, so nothing is rebuilt or re-copied and the flip is one atomic statement. Before the flip, two conditions run in the order that gives each its own honest answer — the ROW says whether this release exists for this tenant at all (404, with no signal about a foreign id), and only then do the BYTES say whether it can still serve (410 GONE when retention has reclaimed them; that rollback target is not coming back, so publish again). Going live also claims the public host and purges the edge, so the release is reachable and no cached predecessor is served. NOT billed: no new content is produced, only a pointer moved.

Scope: a validated principal is required (401 without one) and the site is resolved within that principal's org, so another tenant's slug is a 404.

Request

2 fields.

FieldInTypeRequiredDescription
slugpathstringyesSlug is the site the release belongs to, from the path.
releasepathstringyesRelease is the content-addressed release id ("rel_" + 32 hex chars), from the path.

Response

StatusBodyMeaning
200project.projectsReleaseok
defaultproblem-detailsrefused

200 body — 8 fields.

FieldInTypeAlwaysDescription
activebodyboolean—Active is whether this is the release the site is SERVING right now.
bytesbodyinteger (int64)—Bytes is their total size in bytes.
createdAtbodyinteger (int64)—CreatedAt is when the release was cut, as Unix seconds — not when it was last activated.
objectsbodyinteger (int64)—Objects is how many files the release holds.
releaseIdbodystring—ReleaseID is derived from a DIGEST of the release's own manifest, so identical content is the same release and a release can never be confused with another one.
slugbodystring—Slug is the site this release belongs to.
sourcebodystring—Source is what the release was cut from — the build output or upload it was promoted out of.
urlbodystring—URL is where the site serves.

Failure carries the platform error shape — see Errors.

Examples

hanzo projects releases activate <slug> <release>
import { Configuration, ProjectApi } from 'hanzoai';

const api = new ProjectApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProjectsBySlugReleasesByReleaseActivate({ slug: 'slug', release: 'release' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProjectApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProjectApi(client).post_projects_by_slug_releases_by_release_activate(slug='slug', release='release')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProjectAPI.PostProjectsBySlugReleasesByReleaseActivate(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, project_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = project_api::post_projects_by_slug_releases_by_release_activate(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProjectApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ProjectApi(client).postProjectsBySlugReleasesByReleaseActivate();

The method above is the one at the current release of the document. hanzoai@8.5.914 (npm) and hanzoai@8.5.914 (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl -X POST https://api.hanzo.ai/v1/projects/<slug>/releases/<release>/activate \
  -H "Authorization: Bearer $HANZO_API_KEY"

Tool project, op post_projects_by_slug_releases_by_release_activate — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "project",
         "arguments": {
           "op": "post_projects_by_slug_releases_by_release_activate",
           "input": {
             "slug": "<slug>",
             "release": "<release>"
           }
         }
       }
     }'

Project API · All Hanzo APIs · Interactive reference

Was this page useful?