Docs
Have a token? Manage tokens in the console
POST
/v1/connections/tools/{name}

Calls one tool from List your connection tools by name, with its arguments as a JSON object in args_json.

Needs scope connections:use.

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

name*string

The tool's name, from List your connection tools.

Header Parameters

idempotency-key?string

Makes a retry safe: a repeat with the same key and the same body within a day answers what the first call did (with Idempotency-Replayed: true) instead of running again; the same key with another body is 422 unprocessable. 1 to 255 visible characters; a UUID is a good one.

Length1 <= length <= 255

Request Body

iohr.connections.v1.CallToolRequest; path variables override their fields

application/json
  1. body

iohr.connections.v1.CallToolRequest

args_json?string
name?string

Response Body

iohr.connections.v1.CallToolResponse

application/json
  1. response

iohr.connections.v1.CallToolResponse

ms*string
Formatint64
ok*boolean
result_json*string
tool*string
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.connections.callTool("<name>", { args_json: "<args_json>" });  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.

{  "ms": "string",  "ok": true,  "result_json": "string",  "tool": "string"}