Skip to main content
POST
TypeScript SDK

Authorizations

Authorization
string
header
required

Enter ApiKey <your-api-key> in Authorization, including the ApiKey prefix. In cURL and Python samples, <api-key> means this full value. The TypeScript SDK adds the prefix for you.

Path Parameters

reviewId
string
required

Review ID with prefix trr..

Pattern: ^trr\.[0-9a-f]{8}-[0-9a-f]{4}-[7][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$

Body

application/json

The body is of type object.

Response

The review after the decision

A customer review of one task, with its content, quality criteria and decisions.

checkedRejectsLeft
integer
required

How many more rejects the LLM QA check will check, out of 10. At 0, accept the task or send a forced reject.

Required range: 0 <= x <= 9007199254740991
closedAt
string<date-time> | null
required

Time the review closed, as an ISO 8601 timestamp, or null while it is open.

Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$
deadlineAt
string<date-time>
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.

Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$
id
string
required

Review ID with prefix trr..

Pattern: ^trr\.[0-9a-f]{8}-[0-9a-f]{4}-[7][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
itemId
string
required

Run item ID with prefix plri..

Pattern: ^plri\.[0-9a-f]{8}-[0-9a-f]{4}-[7][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
nodeId
string
required

ID of the generation node whose task is under review.

nodeName
string
required

Name of that generation node.

performer
object
required

Who did the task.

qualityCriteria
object[]
required

The quality criteria a reject can name, as they were when the task reached review.

runId
string
required

Pipeline run ID with prefix plr..

Pattern: ^plr\.[0-9a-f]{8}-[0-9a-f]{4}-[7][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
status
enum<string>
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.

Available options:
needs_review,
returned,
checking,
accepted,
rejected,
expired
submittedAt
string<date-time>
required

Time the task was submitted, as an ISO 8601 timestamp.

Pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$
taskContent
object
required

What the task showed and what was submitted. Project files appear as file proxy URLs.

verdicts
object[]
required

Decisions on this review, oldest first.