Shipeasy
APIOperations

List the operational queue

Returns the unified ops queue (bugs, feature requests, errors, alerts, measurement plans) in work order — highest priority first, oldest first within a…

Returns the unified ops queue (bugs, feature requests, errors, alerts, measurement plans) in work order — highest priority first, oldest first within a priority — so consumers work it top-down. Every filter is applied in SQL before paging, and filters combine with AND. Human-gated holding states (items awaiting human sign-off in the dashboard) are never returned by all/default status.

Filters: type (one item type), status (one lifecycle status, or unresolved — everything not yet resolved/wont_fix), priority (one triage priority), owner (one person or agent), reporter (one filer's email), closedSince (drop items closed before a time), and scope=ready — the items ready to be picked up right now: open, with nobody working them (no open run), and either unowned or reopened (sent back to open after an earlier run finished).

Paging: limit is the page size and offset the number of items to skip. The order is stable, so walk the queue with offset += limit; a page shorter than limit is the last one.

Use case

Pull the open queue to triage — e.g. every bug still open — before working items down one by one.

GET
/api/admin/ops

Authorization

bearerSdkKey
AuthorizationBearer <token>

Pass an admin SDK key as Authorization: Bearer sdk_admin_…. Mint via POST /api/admin/keys with type: "admin".

In: header

Query Parameters

type?|

Filter by item type, or all (the default). Every type a returned item can carry is filterable, including the auto-filed ones.

Default"all"
status?||

Filter by one lifecycle status, unresolved for every status that is not resolved or wont_fix, or all for every status. Defaults to all over HTTP; the CLI and MCP tool default to unresolved, so pass all there to include resolved and won't-fix items. The human-gated holding state (pending_approval) is excluded from unresolved and all, and returned only when requested as the exact status.

Default"all"
priority?|

Filter by triage priority, or all (the default). Items with no priority set are returned only under all.

Default"all"
scope?string

ready narrows to the items ready to be picked up right now: status open, no open run (nobody has acked it and is still working), and either unowned (no person and no agent) or reopened (sent back to open after an earlier run finished). Leave status unset with it. all (the default) applies no such narrowing.

Default"all"
Value in"all" | "ready"
qaQuestions?string

open narrows to the items with at least one unanswered QA question — the backlog QA answers first (read each with ops get, answer with ops qa-questions answer). all (the default) applies no such narrowing.

Default"all"
Value in"all" | "open"
limit?integer

Page size — max items to return (1–500). A page shorter than limit is the last one.

Default200
Range1 <= value <= 500
offset?integer

Number of items to skip before the page starts. Defaults to 0. The order is stable, so offset += limit walks the queue page by page.

Default0
Range0 <= value <= 100000
owner?string

Narrow to items owned by one person OR one agent. Matches a person by users.id, email, or display name, and an agent by connector id, display name, or kebab-case handle — e.g. owner=Claude or owner=alice@acme.dev. Case-insensitive exact match.

reporter?string

Narrow to items filed by one reporter — an email, matched case-insensitive and exact against reporterEmail. Items with no reporter never match. While set, status=all also returns pending_approval items: public intake files every ticket as pending_approval, and a reporter must see the ticket they just filed.

closedSince?string

ISO-8601 timestamp. Items still being worked are always returned; resolved and wont_fix items only when they closed at or after this time (see closedAt). Combines with status like any other filter.

Formatdate-time

Header Parameters

X-Project-Id?string

Project the request operates on. Optional — defaults to the project the SDK key belongs to; pass it only to scope a multi-project key (the generated client sets it once from its configuration, so per-call callers never thread it).

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://shipeasy.ai/api/admin/ops"
[
  {
    "id": "fb_01j7w8a1b2c3d4e5f6g7h8i9j0",
    "number": 7,
    "type": "bug",
    "title": "Checkout button misaligned on mobile",
    "status": "open",
    "priority": "high",
    "source": "team",
    "owner": {
      "user": {
        "id": "usr_01j7w8a1b2c3d4e5f6g7h8i9j0",
        "email": "alice@acme.dev",
        "name": "Alice"
      },
      "agent": null
    },
    "run": null,
    "lastRun": null,
    "createdAt": "2026-06-20T09:14:08.000Z",
    "updatedAt": "2026-06-21T10:02:44.000Z"
  }
]
{
  "error": "Malformed request (bad JSON, missing project scope).",
  "code": "BAD_REQUEST"
}
{
  "error": "Missing or invalid admin SDK key.",
  "code": "UNAUTHORIZED"
}

{
  "error": "Key is valid but not allowed to act on this project.",
  "code": "FORBIDDEN"
}

{
  "error": "The resource does not exist or is not visible to the caller.",
  "code": "NOT_FOUND"
}

{
  "error": "A resource with this name already exists in the project.",
  "code": "ALREADY_EXISTS"
}

{
  "error": "The request body failed structural (schema) validation.",
  "code": "VALIDATION"
}

Was this page helpful?
Updated July 2, 2026