neosourceDocs
Search docs

Request a review from an account

POST/api/repos/{owner}/{repo}/pulls/{number}/review_requests

requestReview

Idempotent on (pr, reviewer). The reviewer receives a `ReviewRequested` notification only on the edge where the request didn't already exist. Self-requests are rejected.

Requires authentication using a bearer token or a session cookie — see tokens and scopes.

curl

curl -X POST 'https://neosource.dev/api/repos/OWNER/REPO/pulls/NUMBER/review_requests' \
  -H 'Authorization: Bearer $NEOSOURCE_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"reviewer_id":"string"}'

fetch

fetch("https://neosource.dev/api/repos/OWNER/REPO/pulls/NUMBER/review_requests", {
  method: "POST",
  headers: {
    Authorization: "Bearer $NEOSOURCE_TOKEN",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"reviewer_id":"string"}),
});

Path parameters

ownerrequired

Repository owner or organization slug.

string

reporequired

Repository name.

string

numberrequired

Change request number.

integerint32

Request bodyrequired

application/json

RequestReviewBody

object

reviewer_idrequired

string

Account being asked to review.

Responses

204Review requested

Standard errors

Bodies documented once for the whole API — see standard errors.

  • 400Bad Request — one of: invalid_input
  • 401Authentication required
  • 403Forbidden — one of: forbidden
  • 404Not Found — one of: not_found
  • 409Conflict — one of: already_exists, conflict, non_fast_forward, github_sync_active
  • 423Locked — one of: busy
  • 429Rate limited — retry after the `Retry-After` header
  • 500Internal server error
  • 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
  • 504Gateway timeout — the request exceeded the server's handling budget