Skip to main content
Requests let workspace members propose source additions or removals and collect reviews before they take effect. Every request reports a status that moves through a fixed state machine. Status changes are recorded with timestamps (opened_at, approved_at, and so on). Use the transition request endpoint to move between author-driven states. Review submissions advance the request with approve, request_changes, or reject. Any transition that is not allowed returns 409 Conflict. Each review has its own lifecycle — see Review status lifecycle.

​
State diagram

​
States

​
Transitions

  • submit moves DRAFT to OPEN and sets opened_at. Only the author can call this.
  • reopen moves CHANGES_REQUESTED or REJECTED back to OPEN and refreshes opened_at.
  • approve, request_changes, and reject on the request are driven by submitting a review.
Content edits (title, description, labels, assignees) and change add/remove are only allowed while the request is in DRAFT. For the full API recipe, see Review source changes.