Replace profile

Chooses a unique lower-case handle, turns the public profile on or off and sets https links.

PUT /v1/reward/me/profile

Reward → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/reward/me/profile`
Method	`PUT`
Operation	`put_reward_me_profile`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Chooses a unique lower-case handle, turns the public profile on or off and sets https links. The public view shows level, lifetime points, badges and claim counts, never an email, org, subject id or redeemable balance.

Request

The document declares no body for PUT /v1/reward/me/profile. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for put_reward_me_profile, which answers from the running route.

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

CLI

SDK

HTTP

MCP

hanzo reward me profile replace

.ts

.py

.go

.rs

.java

import { Configuration, RewardApi } from 'hanzoai';

const api = new RewardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putRewardMeProfile();

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = RewardApi(client).put_reward_me_profile()

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

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

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

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

let result = reward_api::put_reward_me_profile(&cfg, Default::default()).await?;

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

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

var result = new RewardApi(client).putRewardMeProfile();

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 -X PUT https://api.hanzo.ai/v1/reward/me/profile \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches reward through the reward tool, which names its 7 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_reward_me_posts"
         }
       }
     }'

Reward API · All Hanzo APIs · Interactive reference

Was this page useful?

Broken link or missing step? Drop it in #docs on Discord or open a PR.

PreviousCreate posts NextList health