Docs
Have a token? Manage tokens in the console
POST
/v1/rfcs/spaces/{space_id}/documents/{document_id}/review

Approve the current version or ask for changes, as one of the requested reviewers.

Needs scope rfc:write.

Authorization

bearer
headerAuthorizationBearer <token>

An access token from the identity provider: a person's, or a customer's from the client credentials grant with an API key (docs.inorbit.hr). The gateway verifies it; the audience is iohr-api.

Path Parameters

space_id*string

The space's id, lab_ and a ULID, from List spaces.

document_id*string

The document's id, ldoc_ and a ULID, from List documents.

Request Body

iohr.rfcs.v1.SubmitReviewRequest; path variables override their fields

application/json
  1. body

iohr.rfcs.v1.SubmitReviewRequest

decision?string
document_id?string
space_id?string
version?integer
Formatint32

Response Body

iohr.rfcs.v1.SubmitReviewResponse

application/json
  1. response

iohr.rfcs.v1.SubmitReviewResponse

review?

iohr.rfcs.v1.Review

import { ApiError, Public } from "@inorbithr/sdk";// Reads INORBIT_TOKEN, or INORBIT_KEY_ID and INORBIT_KEY_SECRET.const api = Public.fromEnv();try {  const { value } = await api.rfcs.submitReview("<space_id>", "<document_id>", { decision: "<decision>" });  console.log(value);} catch (e) {  if (!(e instanceof ApiError)) throw e;  console.error(`${e.code}: ${e.problem} (request id ${e.raw.requestId})`);}

npm install @inorbithr/sdk. Calls the package's public surface; an operation newer than your package needs the next release or a client generated for your account. The SDKs.

{  "review": {    "decided_at": "string",    "decision": "string",    "display_number": "string",    "document_id": "string",    "kind": "string",    "number": 0,    "requested_at": "string",    "requested_by": "string",    "review_id": "string",    "reviewer": "string",    "space_id": "string",    "space_name": "string",    "title": "string",    "version": 0  }}