Create events
Only the platform principal states an event: the platform's own feeders do, in process, and a client never can.
POST /v1/reward/events
| Address | https://api.hanzo.ai/v1/reward/events |
| Method | POST |
| Operation | post_reward_events |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Only the platform principal states an event: the platform's own feeders do, in process, and a client never can. The event is refused unless it carries exactly the fields the catalog lists for its type, and, for an event that took place on another site, the evidence of where and the checks run there. The same event id again is the same claim, so a retry awards nothing twice. Answers each rule's decision: claimed, skipped, or why it was withheld.
Request
The document declares no body for POST /v1/reward/events. 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 post_reward_events, 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
hanzo reward eventsimport { Configuration, RewardApi } from 'hanzoai';
const api = new RewardApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postRewardEvents();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).post_reward_events()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.RewardAPI.PostRewardEvents(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::post_reward_events(&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).postRewardEvents();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 POST https://api.hanzo.ai/v1/reward/events \
-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"
}
}
}'