Use session signers

Once your user’s have session signers on their wallets, your app can take actions on their behalf. This is done by sending requests to the Privy API to sign transactions with the user’s wallet. Follow the guide below to get started with signing transactions on behalf of users.

​

Requesting signatures

Wallets provisioned for session signers can be used to transact and sign messages on behalf of a user from your server.

To get started, configure the NodeJS SDK or the REST API. This is how your application will make requests to the Privy API to sign transactions on behalf of users. The signing key you configured in the dashboard is the authorization signing key used to produce authorization signatures when submitting requests.

Once you have configured the NodeJS SDK or REST API, your application can send both Ethereum and Solana transactions from a users wallet. Follow the NodeJS or REST API guides in the Using wallets section to learn more about signing requests with wallets.

​

Getting wallets

From your server, you can query Privy to determine what wallets have been provisioned session signers by a given user to allow your app to take actions on their behalf.

const user = await client.getUser({identityToken});

// The `WalletWithMetadata` type can be imported from '@privy-io/server-auth'
const walletsWithSessionSigners = user.linkedAccounts.filter(
  (account): account is WalletWithMetadata =>
    account.type === 'wallet' && account.delegated === true
);

const user = await client.getUser({identityToken});

// The `WalletWithMetadata` type can be imported from '@privy-io/server-auth'
const walletsWithSessionSigners = user.linkedAccounts.filter(
  (account): account is WalletWithMetadata =>
    account.type === 'wallet' && account.delegated === true
);

https://auth.privy.io/api/v1/users/<user-did>

curl --request GET https://auth.privy.io/api/v1/users/<user-did> \
-u "<your-privy-app-id>:<your-privy-app-secret>" \
-H "privy-app-id: <your-privy-app-id>"