Sign

namera.sign(request) prepares, validates, and completes a signature using the selected session key. It does not send a transaction.

UsageCopy Anchor Link

Install @namera-ai/sdk and set NAMERA_API_KEY. Replace example IDs with resources available to your credential.

import { namera } from "./client";
const message = "Hello from Namera";

const signed = await namera.sign({
  namespace: "eip155",
  walletId: "0199dfe1-0000-7000-8000-000000000001",
  sessionKeyId: "0199dfe1-0000-7000-8000-000000000002",
  chainId: "eip155:84532",
  type: "message",
  message,
});

if (!signed.success) throw new Error(signed.error.message);

console.log(signed.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.

• namespace ("eip155"): Chain namespace.
• walletId (string): Account UUID.
• chainId (SupportedEvmChainId): Signing network.
• account (`0x${string}`): Smart-account address.
• signature (`0x${string}`): Smart-account signature, not a bare EOA signature.
• type ("message" | "typed-data"): Payload kind.

Example ResponseCopy Anchor Link

{
  "namespace": "eip155",
  "walletId": "0199dfe1-0000-7000-8000-000000000001",
  "chainId": "eip155:84532",
  "account": "0x1111111111111111111111111111111111111111",
  "signature": "0x0000000100111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111b",
  "type": "message"
}

ParametersCopy Anchor Link

Pass a SignRequest object. The selected session needs installed signature authority and an API policy permitting the payload.

namespaceCopy Anchor Link

• Type: "eip155"
• Required

The blockchain namespace. Use "eip155" for every currently supported Namera network. This is not a chain ID; select the specific network with chainId.

import { namera } from "./client";
const message = "Hello from Namera";

const signed = await namera.sign({
  namespace: "eip155", 
  walletId: "0199dfe1-0000-7000-8000-000000000001",
  sessionKeyId: "0199dfe1-0000-7000-8000-000000000002",
  chainId: "eip155:84532",
  type: "message",
  message,
});

if (!signed.success) throw new Error(signed.error.message);

console.log(signed.data);

walletIdCopy Anchor Link

• Type: string
• Required

The account UUID returned by wallets.list() or wallets.get(). Pass its id, not its onchain address. The account must be accessible to the client’s credential.

import { namera } from "./client";
const message = "Hello from Namera";

const signed = await namera.sign({
  namespace: "eip155",
  walletId: "0199dfe1-0000-7000-8000-000000000001", 
  sessionKeyId: "0199dfe1-0000-7000-8000-000000000002",
  chainId: "eip155:84532",
  type: "message",
  message,
});

if (!signed.success) throw new Error(signed.error.message);

console.log(signed.data);

sessionKeyIdCopy Anchor Link

• Type: string
• Required

The session-key UUID returned by sessionKeys.list() or sessionKeys.get(). This identifies the delegated session, not its signing key or network installation. Your credential must have an active grant for this key.

For execution or signing, choose a key belonging to walletId with a confirmed installation on chainId and permissions that allow the requested operation.

import { namera } from "./client";
const message = "Hello from Namera";

const signed = await namera.sign({
  namespace: "eip155",
  walletId: "0199dfe1-0000-7000-8000-000000000001",
  sessionKeyId: "0199dfe1-0000-7000-8000-000000000002", 
  chainId: "eip155:84532",
  type: "message",
  message,
});

if (!signed.success) throw new Error(signed.error.message);

console.log(signed.data);

chainIdCopy Anchor Link

• Type: SupportedEvmChainId
• Required

The target network in CAIP-2 format. For Base Sepolia, use "eip155:84532", not 84532 or "84532". Use the network on which the account will execute, sign, or verify the payload.

The SDK restricts this field to the supported network IDs. Network availability is also checked by the API.

import { namera } from "./client";
const message = "Hello from Namera";

const signed = await namera.sign({
  namespace: "eip155",
  walletId: "0199dfe1-0000-7000-8000-000000000001",
  sessionKeyId: "0199dfe1-0000-7000-8000-000000000002",
  chainId: "eip155:84532", 
  type: "message",
  message,
});

if (!signed.success) throw new Error(signed.error.message);

console.log(signed.data);

typeCopy Anchor Link

• Type: "message" | "typed-data"
• Required

Selects the payload format. Use message with "message" or typedData with "typed-data". Do not supply both payload fields.

messageCopy Anchor Link

• Type: string
• Required when: type is "message"

The exact UTF-8 text to sign or verify. Whitespace and capitalization are part of the payload. A string such as "0x1234" is text, not raw bytes.

typedDataCopy Anchor Link

• Type: EvmTypedData
• Required when: type is "typed-data"

An EIP-712 payload containing domain, types, primaryType, and message. Use the identical payload when verifying its signature.

import type { EvmTypedData } from "@namera-ai/sdk";

const typedData = {
  domain: {
    name: "Namera Example",
    version: "1",
    chainId: 84532,
    verifyingContract: "0x3333333333333333333333333333333333333333",
  },
  types: { Greeting: [{ name: "contents", type: "string" }] },
  primaryType: "Greeting",
  message: { contents: "Hello from Namera" },
} satisfies EvmTypedData;

typedData.domainCopy Anchor Link

• Type: EvmTypedData["domain"]
• Required

The signing domain. Its fields are optional: name and version are strings; chainId is a nonnegative integer; verifyingContract is a 20-byte address; salt is a 32-byte hex value. Unlike the request’s CAIP-2 chainId, this domain uses a number such as 84532. Use the domain expected by the verifying application.

typedData.typesCopy Anchor Link

• Type: Record<string, readonly { name: string; type: string }[]>
• Required

Definitions of the structs used by the payload. Struct names, field names, and field types must be nonempty strings. Each struct needs at least one field.

typedData.primaryTypeCopy Anchor Link

• Type: string
• Required

The root struct name from types, such as "Greeting". It determines how the message fields are encoded.

typedData.messageCopy Anchor Link

• Type: Record<string, Json>
• Required

Values matching the root struct. Use JSON-compatible values. Represent large integers as decimal strings, not JavaScript bigint, to preserve precision.

Sign typed dataCopy Anchor Link

Use type: "typed-data" with the complete payload. The session’s signature policy must permit its domain and primary type. Replace the domain’s contract address with the one expected by your application.

import type { EvmTypedData } from "@namera-ai/sdk";
import { namera } from "./client";

const typedData = {
  domain: {
    name: "Namera Example",
    version: "1",
    chainId: 84532,
    verifyingContract: "0x3333333333333333333333333333333333333333",
  },
  types: {
    Greeting: [{ name: "contents", type: "string" }],
  },
  primaryType: "Greeting",
  message: { contents: "Hello from Namera" },
} satisfies EvmTypedData;

ErrorsCopy Anchor Link

Signature policy, authorization, billing, and signing failures return success: false. Prepared-payload or signature validation failures use kind: "signer". See Handling Results and Errors for shared authentication, transport, and contract errors.

Guides: Sign Messages and Sign Typed Data.