Permissions
Understand what your session key is allowed to execute and sign.
A valid credential is only the first requirement. Your application also needs access to a session key whose permissions allow execution or signing. Workspace management is a separate, explicitly issued authority.
Workspace management permissions
In Settings → Workspace → API keys, explicitly select the permissions your backend needs. Existing keys have none. Permissions cover all existing and future accounts and sessions in the key’s workspace, never another workspace.
| Permission | Allows |
|---|---|
wallet:read | Read all workspace accounts and their public owner descriptors. |
wallet:create | Create managed or passkey-owned accounts. |
session-key:read | Read all workspace sessions and this actor’s owner operations. |
session-key:create | Create sessions on any workspace account. |
session-key:install | Explicitly approve a stored session installation. |
session-key:uninstall | Explicitly approve removal of a network installation. |
session-key:revoke | Revoke a session’s Namera access and grants. |
Only users holding the corresponding management authority may issue it. Keys do not inherit their creator’s complete role and cannot issue other keys or expand their own permissions. Create a replacement key to change permissions.
A key with session creation and installation authority can grant itself full control of managed accounts. Reserve these permissions for trusted backend wallet administration. API-key permission does not replace a passkey owner’s signature. Creating a session grants its creating API-key actor access; management access alone does not grant execution access to pre-existing sessions.
Passkey registration also requires an exact application origin allowlisted at key issuance. Keep the API key on your authenticated backend and bind ceremonies and operation approvals to your application users.
See account management guides.
What Allows a Transaction
Before executing, check that:
- Your API key or OAuth authorization has a grant to the selected session key.
- The key is active and its installation is confirmed on the target network.
- The installation is within its validity period and allows the recipient, contract calls, and amounts you want to use.
Configure these in the Namera dashboard. For a 0.001 ETH transfer, allow the recipient and a native-token allowance that covers the transfer, then approve the installation on that network.
Onchain Permissions and API Policies
Onchain permissions are approved by the account owner and enforced by the account's contracts. They define transaction authority, including allowed targets, functions, spending allowances, and validity periods.
API policies govern delegated signatures through Namera: signature type, allowed networks, and validity windows. Transaction spending and gas restrictions come from installed onchain permissions. All applicable policies must pass; one policy cannot override another denial.
Policies cannot expand authority
An API policy cannot allow a transaction that the onchain permissions reject. API policies apply to requests through Namera, not calls made outside it.
Inspect a Session Key
Replace the example ID with the session key you plan to use:
import { NameraClient } from "@namera-ai/sdk";
const namera = new NameraClient({
apiKey: process.env.NAMERA_API_KEY!,
});
const result = await namera.sessionKeys.get("0199dfe1-0000-7000-8000-000000000002");
if (!result.success) throw new Error(result.error.message);
const session = result.data;
console.log(result.data);Read policies for API restrictions. Each entry in installations includes its
chainId, status, and approved authorization. A usable installation has
status installed; also check its validity period and permissions.
Check a Call Before Sending
Install viem if you have not already, then simulate with the same account,
session key, network, and calls you intend to execute:
npm install viemimport { parseEther } from "viem";
const simulation = await namera.executions.simulate({
namespace: "eip155",
walletId: session.walletId,
sessionKeyId: session.id,
chainId: "eip155:84532",
calls: [
{
to: "0x2222222222222222222222222222222222222222",
value: parseEther("0.001"),
data: "0x",
},
],
});
if (!simulation.success) throw new Error(simulation.error.message);
console.log(simulation.data);Replace the recipient with the address allowed by your key. Simulation does not submit a transaction or reserve billing allowance. Review the call results; balances, installed permissions and available allowance can change before execution.
Message and Typed Data Signing
Signing needs explicit signature authority in the installation
(allowSignatures) and an API signature policy permitting the requested type:
message or typed-data. Transaction permissions alone do not enable signing.
Typed-data policies can restrict the chain, verifying contract, primary type, and domain. They do not limit the amounts inside a signed message.
Signature authority is separate
Transaction spending limits and expiry do not constrain onchain signature authority. Uninstall that authority onchain to revoke it.
Next, choose a supported network.