Your First Review

Pull requests arrive by GitHub sync — IonWarp writes them, you read them. That is why Pull Requests is read-only over REST: a write here would be a claim about GitHub's state that GitHub did not make.

List pull requests — GET /api/v1/pull-requests

curl "https://ionwarp.com/api/v1/pull-requests?state=open" \
  -H "Authorization: Bearer $DASH_API_KEY" \
  -H "Project-ID: pr_acme"

Which pull requests are still waiting on changes?

data_query {
  "collection": "pull_requests",
  "where": {
    "state": "open"
  }
}

{
  "object": "list",
  "data": [
    {
      "object": "pull-request",
      "id": "obj_123",
      "number": 630,
      "title": "Collapse the review dispatch fast path",
      "state": "open",
      "created_at": "2026-07-25T12:00:00.000Z",
      "updated_at": "2026-07-25T12:00:00.000Z"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

A review posts its result to the PR as comments and stamps the outcome on the pull request row (review_status, last_reviewed_at), with per-reviewer telemetry on the run — nothing about the outcome lives only in prose.

The lineup of Reviewers is configurable — see Reviewers & Models. Output lands in two places: the PR comment, and the project timeline.

Next: Your First Scorecard.