Create dispute
Records that the caller's org disputes one payment it is party to — for the org's admins.
POST /v1/event/economic/dispute
| Address | https://api.hanzo.ai/v1/event/economic/dispute |
| Method | POST |
| Operation | post_event_economic_dispute |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Records that the caller's org disputes one payment it is party to — for the org's admins. A dispute is a record both parties read beside the payment, and it changes nothing about it: the amount, the parties and the tax year stay as the rail stated them, because only the rail that moved the money restates a payment.
Request
2 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
event | body | string | yes | Event is the id of the economic event disputed. |
reason | body | string | yes | Reason is what the caller's org says is wrong, at most 1024 characters. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | event.EconomicDispute | ok |
default | problem-details | refused |
200 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
at | body | integer (int64) | — | At is when the dispute was filed, unix seconds. |
by | body | string | — | By is the org that disputes it: one of the event's two parties. |
event | body | string | — | Event is the id of the event disputed. |
reason | body | string | — | Reason is what the party says is wrong. |
Failure carries the platform error shape — 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, EventApi } from 'hanzoai';
const api = new EventApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postEventEconomicDispute({ event: "<event>", reason: "<reason>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import EventApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = EventApi(client).post_event_economic_dispute(event="<event>", reason="<reason>")cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.EventAPI.PostEventEconomicDispute(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, event_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = event_api::post_event_economic_dispute(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EventApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new EventApi(client).postEventEconomicDispute();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/event/economic/dispute \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"event": "<event>",
"reason": "<reason>"
}'MCP declares no tool for event — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?