HIhify
Order Requests

Update a Order request

Assignment and attribute changes are applied in one transaction: a rejected update also rolls back the assignment. processing_state, processing_details and next_attempt_at are job-owned and not writable here.

put/v1/order_requests/{id}

Request

  • Base URL
    https://api.hify.club
  • Auth
    API key in header X-User-Token

Request body

Example request

{
  "order_request": {
    "assignee": "priya@hify.club"
  }
}

Response

Order request updated

idinteger
type'HighlightRequest' | 'ReplayRequest' | 'ShortRequest'
status'open' | 'in_progress' | 'in_review' | 'done' | 'archived'
assigneestring nullable

Email of the current human owner (annotator, then editor). Null when unassigned.

assigned_atstring date-time nullable
attention_state'annotating' | 'ready_to_bundle' | 'processing' | 'needs_editor' | 'editing' | 'in_review' | 'stuck' | 'done' nullable

Ops-facing pipeline stage group (one group = one owner). Grouped from the granular stored/derived states; the granular detail per row stays in processing_state and processing_message. Null for rows with no stage (e.g. pre-contract replays).

stage_entered_atstring date-time nullable

When the current stage was entered. Poll rewrites do not move it.

processing_statestring nullable

Machine-readable stage stored by the owning job. Job-owned; not writable via this API.

processing_detailsobject

Structured facts behind processing_state; schema per request type.

processing_messagestring nullable

Human-readable rendering of processing_state + processing_details.

next_attempt_atstring date-time nullable

When the system will next act. Null means nothing is scheduled (finished, or stuck).

userobject
gameobject
orderobject

Example response

{
  "assignee": "priya@hify.club",
  "processing_message": "Delivered 3/12 segments (camera 12); watching for the rest"
}

Changes

No recorded changes to this operation across all 1 revision of this API.