sessionKeys.getOperation

namera.sessionKeys.getOperation() read the status of an installation or removal operation.

UsageCopy Anchor Link

Install @namera-ai/sdk and set NAMERA_API_KEY on your backend. IDs and responses below are illustrative fixtures; replace IDs with your own resources.

import { namera } from "./client";
const result = await namera.sessionKeys.getOperation("0199dfe1-0000-7000-8000-000000000014");
if (!result.success) throw new Error(result.error.message);

console.log(result.data);

ReturnsCopy Anchor Link

API methods return a Promise<NameraResult<T, E>>. When success is true, data contains the value described below and error is null. On failure, data is null and error describes the failure.

The JSON example shows the complete successful data, with illustrative values. Date-time values use ISO strings in JSON; bigint values use decimal strings. See Handling Results and Errors for the error shape.

Returns operationId and status: awaiting-signature, signed, submitted, confirmed, failed, expired, or cancelled. Only confirmed establishes successful receipt confirmation.

{
  "operationId": "0199dfe1-0000-7000-8000-000000000014",
  "status": "confirmed"
}

ParametersCopy Anchor Link

operationIdCopy Anchor Link

Type: string. Required. Resource UUID returned by creation, preparation, or recovery; not an address or transaction hash.

import { namera } from "./client";
const result = await namera.sessionKeys.getOperation("0199dfe1-0000-7000-8000-000000000014"); 
if (!result.success) throw new Error(result.error.message);

console.log(result.data);

Behavior and errorsCopy Anchor Link

Requires session-key:read. API keys can poll only operations initiated by that same actor. OPERATION_UNAVAILABLE covers missing, foreign-workspace, and other-actor operations. A missing receipt leaves an operation pending; do not start another installation simply because polling is slow.