issues

File Work Order

File a build item straight into the drain's queue, on the manager's own service principal -- Frederick, 2026-09-30: "I want everything on the cloud code seat... bring the Mac completely out of the loop for Roost." The manager no longer dispatches a builder as a local subprocess in a Mac worktree; it calls this route instead, and a cloud seat claims and builds the issue exactly like any other (see service.file_work_order's own docstring for the full contract, including why ruling_reference is required and never optional).

post/api/issues/work-orders

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/issues/work-orders
  • Auth: none declared

Request body

titlestring required
briefstring required
ruling_referencestring required
prioritystring
base_branchstring nullable
target_systemstring nullable

Response

Successful Response

object required

Changes

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