List metadata

Returns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a revision.

GET /v1/deploy/applications/{name}/revisions/{revision}/metadata

Deploy → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/deploy/applications/{name}/revisions/{revision}/metadata`
Method	`GET`
Operation	`get_deploy_applications_by_name_revisions_by_revision_metadata`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the argocd RevisionMetadata for one revision of one application — what the detail view shows beside a revision.

An App CR is IMAGE-pinned rather than commit-pinned: the deploy names an image tag, and the git source this projection reports is the display-only manifest repo, not the application's own source. Nothing in this process can read a commit's author or message for an arbitrary revision. So rather than 404 (which the SPA turns into an error toast) or invent a git author, it answers the HONEST minimum: date is when the App CR was created, message is the revision asked for — with the empty revision and "HEAD" resolving to the image tag the CR declares — and author is empty. An over-long revision is truncated before it is echoed back.

Tenant-scoped exactly like the application read.

Request

2 fields.

Field	In	Type	Required	Description
`name`	path	string	yes	Name is the application to read, from the path.
`revision`	path	string	yes	Revision is the revision to describe, from the path.

Response

Status	Body	Meaning
`200`	deploy.argoRevisionMetadata	ok
`default`	problem-details	refused

200 body — 5 fields.

Field	In	Type	Always	Description
`author`	body	string	—	Author is the commit author.
`date`	body	string	—	Date is when the App CR was created, RFC 3339 UTC — the only real timestamp there is here.
`message`	body	string	—	Message is the revision asked for, echoed back — not a commit message.
`signatureInfo`	body	string	—	SignatureInfo is the GPG verification result for the revision.
`tags`	body	string[]	—	Tags are the git tags pointing at the revision.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo deploy applications revisions metadata <name> <revision>

.ts

.py

.go

.rs

.java

import { Configuration, DeployApi } from 'hanzoai';

const api = new DeployApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getDeployApplicationsByNameRevisionsByRevisionMetadata({ name: 'name', revision: 'revision' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import DeployApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = DeployApi(client).get_deploy_applications_by_name_revisions_by_revision_metadata(name='name', revision='revision')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.DeployAPI.GetDeployApplicationsByNameRevisionsByRevisionMetadata(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, deploy_api};

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

let result = deploy_api::get_deploy_applications_by_name_revisions_by_revision_metadata(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.DeployApi;

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

var result = new DeployApi(client).getDeployApplicationsByNameRevisionsByRevisionMetadata();

curl https://api.hanzo.ai/v1/deploy/applications/<name>/revisions/<revision>/metadata \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches deploy through the deploy tool, which names its 11 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_deploy_applications"
         }
       }
     }'

Deploy API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList resource tree — GET /v1/deploy/applications/{name}/resource-tree NextList syncwindows