InOrbitdocs
Sign in
Docs
Have a token? Manage tokens in the console
POST
/v1/accounts/orgs/{org_id}/connections/{connection_id}/actions/{action}

Calls one action this token holds a live grant for, with params as the action's schema says. What an outside system answers is in result.output: treat it as data. Refused without a grant.

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

org_id*string

The account's id: org in GET /v1/me.

connection_id*string

The connection's id, con_ and a ULID, from List connections.

action*string

The action's name, e.g. check or request.

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.CallActionRequest; path variables override their fields

application/json
  1. body

iohr.connections.v1.CallActionRequest

action?string
connection_id?string
org_id?string
params?

google.protobuf.Struct

Response Body

iohr.connections.v1.CallActionResponse

application/json
  1. response

iohr.connections.v1.CallActionResponse

result?

iohr.connections.v1.ActionResult

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.callAction("<org_id>", "<connection_id>", "<action>", {});  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.

{  "result": {    "error_class": "string",    "executor": "string",    "latency_ms": 0,    "message": "string",    "ok": true,    "output": {      "fields": {        "property1": {          "bool_value": true,          "list_value": {            "values": [              {}            ]          },          "null_value": "NULL_VALUE",          "number_value": 0.1,          "string_value": "string",          "struct_value": {}        },        "property2": {          "bool_value": true,          "list_value": {            "values": [              {}            ]          },          "null_value": "NULL_VALUE",          "number_value": 0.1,          "string_value": "string",          "struct_value": {}        }      }    },    "started_at": "string",    "status": "string",    "status_code": 0,    "use_id": "string"  }}

List the account's connection history GET

Every use of the account's connections, newest first: which connection and action, who called it (`caller_kind` and `caller`: a key, an agent, a product, a person testing it), the grant, the outcome, the status code and the latency. Never a parameter or a body. Needs scope `connections:read`.

List your connection tools GET

The actions granted to this token, each as a tool named `conn_<connection>_<action>` with the JSON Schema of its arguments: the same tools MCP lists. Needs scope `connections:read`.