Fetch a profile photo
Streams a profile photo's raw BYTES. This is the address stored on the user's IAM record and rendered directly by an `<img>`, so it takes no credentials —…
GET /v1/account/avatar/{org}/{user}/{digest}
| Address | https://api.hanzo.ai/v1/account/avatar/{org}/{user}/{digest} |
| Method | GET |
| Operation | get_account_avatar_by_org_by_user_by_digest |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Streams a profile photo's raw BYTES. This is the address stored on the user's IAM record and rendered directly by an <img>, so it takes no credentials — the 64-hex content digest in the path is the capability, and it can only be produced by someone who already has the image.
The Content-Type is derived from the stored bytes and the response carries nosniff, so only a real raster image is ever served and only under its true type. Anything else — a miss, a malformed path, an object that is not an image — is one 404, and a hit caches for a year because the address is the content.
Request
3 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
org | path | string | yes | |
user | path | string | yes | |
digest | path | string | yes |
Response
The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, AccountApi } from 'hanzoai';
const api = new AccountApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAccountAvatarByOrgByUserByDigest({ org: 'org', user: 'user', digest: 'digest' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AccountApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AccountApi(client).get_account_avatar_by_org_by_user_by_digest(org='org', user='user', digest='digest')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.AccountAPI.GetAccountAvatarByOrgByUserByDigest(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, account_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = account_api::get_account_avatar_by_org_by_user_by_digest(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.AccountApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new AccountApi(client).getAccountAvatarByOrgByUserByDigest();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (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 https://api.hanzo.ai/v1/account/avatar/<org>/<user>/<digest> \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches account through the account tool, which names its 8 operations with its own verbs — this one among them, under a name only the door 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": "get_appearance"
}
}
}'How is this guide?