Schemas
Check the schemas
Have a token? Manage tokens in the console
GET
What the schemas check finds in the folder: layout, manifest, references and the placeholder lint, the same findings in the same order as schemas:check prints.
Needs scope schemas:read.
bearerheader
AuthorizationBearer <JWT>An access token from the identity provider: a person's, or a customer's from the client credentials grant with an API key (developers.inorbit.hr). The gateway verifies it; the audience is iohr-api.
failed_only?booleanOnly the findings that failed.
iohr.schemas.v1.CheckSchemasResponse
application/json- response
iohr.schemas.v1.CheckSchemasResponse
checked*integerFormat
int32checked_at_unix*stringFormat
int64failed*integerFormat
int32findings*array<>SDK
HTTP
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.schemas.checkSchemas(); console.log(value);} catch (e) { if (!(e instanceof ApiError)) throw e; console.error(`${e.code}: ${e.problem} (request id ${e.raw.requestId})`); process.exitCode = 1;}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.
Example Response
{ "checked": 0, "checked_at_unix": "string", "failed": 0, "findings": [ { "detail": "string", "name": "string", "ok": true } ]}