Your First Review
Reviews start on their own for every watched PR; here is how to start one by hand and read what it found.
Checklist step
first_review of the onboarding checklist the product shows you, told API-first.Once the repository is connected, every pull request that opens or gets a new push is reviewed without you doing anything. To review a specific PR now — with the reviewers and models you choose — start one from the API:
REVIEW_ID=$(curl --fail-with-body "https://ionwarp.com/api/v1/reviews" \
-H "Authorization: Bearer $IONWARP_API_KEY" \
-H "Project-ID: $PROJECT_ID" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: acme-reviews.create-1' \
-d '{"pr":42,"reviewers":["code-review","security-review@google/gemini-3.8-flash"]}' | jq -er '.id')Then read it by the id it answered with. run is the receipt (status, cost,
one row per reviewer) and findings are inlined once the run is done:
curl --fail-with-body "https://ionwarp.com/api/v1/reviews/$REVIEW_ID" \
-H "Authorization: Bearer $IONWARP_API_KEY" \
-H "Project-ID: $PROJECT_ID"Pull requests themselves arrive by GitHub sync — IonWarp writes them, you read
them — so Pull Requests is read-only over
REST: a write there would be a claim about GitHub's state that GitHub did not
make. Where each review got to is stamped on the PR row (review_status,
last_reviewed_at), and with delivery: "github" the result is posted on the
PR as comments and the IonWarp / Review check — the full lifecycle is on
Reviews.
Next: Your First Scorecard.