Docs
Have a token? Manage tokens in the console
GET
/v1/rfcs/spaces/{space_id}

One space: its name, description, slug and counts. A space you cannot see answers 404, the same as one that does not exist.

Needs scope rfc:read.

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.

Response Body

iohr.rfcs.v1.GetSpaceResponse

application/json
  1. response

iohr.rfcs.v1.GetSpaceResponse

space?

iohr.rfcs.v1.Space

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.getSpace("<space_id>");  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.

{  "space": {    "account_id": "string",    "awaiting_review": 0,    "created_at": "string",    "description": "string",    "documents": 0,    "name": "string",    "open": 0,    "slug": "string",    "space_id": "string",    "updated_at": "string"  }}