Skip to main content
Only teams with customer review enabled: other teams get 403 The "customerReview" feature is not enabled for this team. Reject the task under review, naming the quality criteria it fails and explaining what is wrong. The LLM QA check then checks this evidence: if it agrees, the reject is final, the item fails at this node, and nothing is billed for the task; otherwise the review returns with the check’s reason for a new decision, or expires if its deadline has passed. With force, the check is skipped and the reject is final at once; a forced reject is accepted only after the LLM QA check has returned a reject of this review, so reject without force first.

Signature

Method signature on client.reviews:

Parameters

string
required
Review ID with prefix trr..
string[]
required
IDs of the quality criteria the task fails: at least one, each named once.
string
required
What is wrong with the task, at most 10000 characters.
false | true
Skip the LLM QA check and reject at once. The reject is final and does not count toward the checked rejects. Allowed only after the LLM QA check has returned a reject of this review; otherwise the response is 409. Defaults to false.

Returns

Promise<Review> A customer review of one task, with its content, quality criteria and decisions.
ReviewId
required
Review ID with prefix trr..
RunId
required
Pipeline run ID with prefix plr..
RunItemId
required
Run item ID with prefix plri..
string
required
ID of the generation node whose task is under review.
string
required
Name of that generation node.
ReviewStatus
required
Review status. needs_review: waiting for the first decision. returned: the LLM QA check did not confirm the last reject, so the review waits for a new decision. checking: the LLM QA check is checking a reject, and decisions are refused until it answers. accepted: the team accepted the task. rejected: the reject is final, either forced or confirmed by the LLM QA check. expired: the deadline passed while the review was open, whether it waited for a decision or was checking a reject the check then did not confirm, so the task was accepted automatically.
string
required
Time the task was submitted, as an ISO 8601 timestamp.
string
required
Deadline for a decision, as an ISO 8601 timestamp. From then on the review takes no decisions, but it closes a little later: a review waiting for a decision expires shortly after the deadline, and its task is accepted automatically (the expert is paid and the task is billed); a review checking a reject closes when the LLM QA check answers.
string | null
required
Time the review closed, as an ISO 8601 timestamp, or null while it is open.
object
required
Who did the task.
object
required
What the task showed and what was submitted. Project files appear as file proxy URLs.
ReviewQualityCriterion[]
required
The quality criteria a reject can name, as they were when the task reached review.
ReviewVerdict[]
required
Decisions on this review, oldest first.
number
required
How many more rejects the LLM QA check will check, out of 10. At 0, accept the task or send a forced reject.

Errors

HTTP errors throw PotatoApiError. The endpoint documents these error responses: HTTP endpoint: POST /reviews/{reviewId}/reject.