Skip to main content

Creating a personal access token

Step-by-step guide to create a PAT and configure your SDK
Personal Access Tokens (PATs) are used to automate actions on behalf of a user. PATs are linked to your user. The effective permissions of a PAT are always the intersection of the user’s permissions and the token’s own permissions, enforced on every request. This means you can create a read-only PAT to monitor transactions in your wallet without reducing the permissions of your user. Since PATs are tied to a user, if the user is deactivated, all their PATs stop working (the backend validates the user’s active status on every request). Reactivating the user restores PAT access. Because of this, PATs are not meant to be used for server tasks. If you have a long-lived task, it is recommended that you use a Service Account instead, as Service Accounts are not tied to a specific user. This also means that a Service Account can have different permissions from the user that created the Service Account, giving you the ability to limit user permissions without affecting server tasks.

Personal Access Token object

dateCreated
string
required
credId
string
required
isActive
boolean
required
kind
enum<string>
required

Access token kind.

Available options:
Pat,
ServiceAccount,
Token,
Code,
Recovery,
Temp,
Application
linkedUserId
string
required
linkedAppId
string
required
name
string
required
orgId
string
required
permissionAssignments
object[]
required
publicKey
string
required
tokenId
string
required
accessToken
string
Last modified on April 16, 2026