Create feedback
Rates the other party of a settled job — the seller when the caller's org bought, the buyer when it sold — once per party per job, and never edited.
POST /v1/marketplace/jobs/{id}/feedback
| Address | https://api.hanzo.ai/v1/marketplace/jobs/{id}/feedback |
| Method | POST |
| Operation | post_marketplace_jobs_by_id_feedback |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Rates the other party of a settled job — the seller when the caller's org bought, the buyer when it sold — once per party per job, and never edited. A job counts as settled once it was released, or refunded after the seller took it on; one cancelled or declined before any work earns nothing. What buyers say of a seller is its listing's and its own reputation in the shop. It answers 201 with the feedback recorded.
Request
4 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes | ID is the job, from the path. |
comment | body | string | — | Comment is the party's words, at most 4096 characters. |
id | body | string | — | ID is the job, from the path. |
rating | body | integer (int64) | — | Rating is 1 to 5 stars. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | marketplace.Feedback | created |
default | problem-details | refused |
201 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
about | body | string | — | About is the other party of the job, the org it is about. |
at | body | integer (int64) | — | At is when, unix seconds. |
comment | body | string | — | Comment is the party's words, at most 4096 characters. |
from | body | string | — | From is the org that gave it. |
job | body | string | — | Job is the job it is about. |
listing | body | string | — | Listing is the listing the job was hired through; empty for a direct offer. |
rating | body | integer (int64) | — | Rating is 1 to 5 stars. |
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, MarketplaceApi } from 'hanzoai';
const api = new MarketplaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketplaceJobsByIdFeedback({ id: 'id', comment: "<comment>", id: "<id>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MarketplaceApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MarketplaceApi(client).post_marketplace_jobs_by_id_feedback(id='id', comment="<comment>", id="<id>")cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.MarketplaceAPI.PostMarketplaceJobsByIdFeedback(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, marketplace_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = marketplace_api::post_marketplace_jobs_by_id_feedback(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MarketplaceApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new MarketplaceApi(client).postMarketplaceJobsByIdFeedback();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/marketplace/jobs/<id>/feedback \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"comment": "<comment>",
"id": "<id>"
}'MCP reaches marketplace through the marketplace tool, which names its 6 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": "get_marketplace"
}
}
}'How is this guide?