Create recheck

Looks at one of your pending or removed posts now, with the same checks as the daily look, and adds the look to its history.

POST /v1/reward/me/posts/{id}/recheck

Reward → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/reward/me/posts/{id}/recheck`
Method	`POST`
Operation	`post_reward_me_posts_by_id_recheck`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Looks at one of your pending or removed posts now, with the same checks as the daily look, and adds the look to its history. A removed post that is back up and carries your link is held again and its week starts over. Asked at most ten times an hour.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes

Response

Status	Body	Meaning
`200`	reward.postView	ok
`default`	problem-details	refused

200 body — 15 fields.

Field	In	Type	Always	Description
`checks`	body	reward.Check[]	—	Checks is every look at the post, oldest first.
`checks[].author_match`	body	string	—	AuthorMatch is whether the author is the member's linked identity: yes, no or unknown.
`checks[].fetched_at`	body	string (date-time)	—	FetchedAt is when the source was fetched.
`checks[].public`	body	boolean	—	Public is whether the source is readable by anyone.
`checks[].ref_found`	body	boolean	—	RefFound is whether the member's own ref code was found.
`checks[].status`	body	integer (int64)	—	Status is the HTTP status the fetch answered.
`countsAt`	body	string (date-time)	—
`daysLeft`	body	integer (int64)	—
`id`	body	string	—
`network`	body	string	—
`note`	body	string	—	Note says why a post was removed.
`since`	body	string (date-time)	—	Since is when the post's week began; CountsAt when it counts, and DaysLeft the days until then.
`status`	body	string	—	Status is pending (held for its week, counts for nothing), verified (it stayed up and was put to staff), removed (it earns nothing) or review (staff decide it by hand).
`url`	body	string	—
`week`	body	string	—	Week is the ISO week the post was published in; a post in a later week can earn again.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo reward me posts recheck <id>

.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.postRewardMePostsByIdRecheck({ id: 'id' });

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_me_posts_by_id_recheck(id='id')

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

resp, _, err := client.RewardAPI.PostRewardMePostsByIdRecheck(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_me_posts_by_id_recheck(&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).postRewardMePostsByIdRecheck();

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/me/posts/<id>/recheck \
  -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 check NextCreate scan