API Authorization
Identity & Access Management
Wallets & Transactions
Management
Webhooks
Copy
Ask AI
{
"username": "<string>",
"name": "<string>",
"userId": "us-6b58p-r53sr-rlrd3l5cj3uc4ome",
"kind": "AccountUser",
"credentialUuid": "<string>",
"orgId": "<string>",
"isActive": true,
"isServiceAccount": true,
"isRegistered": true,
"isSSORequired": true,
"permissionAssignments": [
{
"permissionName": "<string>",
"permissionId": "<string>",
"assignmentId": "<string>",
"operations": [
"<string>"
]
}
],
"permissions": [
"<string>"
]
}Users represent people with access to the Dfns platform. These can be either Employees of your company or end users of your service who do not work for you (either consumers or corporate clients). Alternatively, you can create Service Accounts, which serve as API keys for programmatic access to the system.
When you call Create User providing an email address, an email will be sent from Dfns to the user to onboard them to the Dfns dashboard. Note in most cases, you will only do this for Employees and can accomplish this from the Settings section of our dashboard without using the API directly.
If you are implementing Delegated Signing in which your user has full control over a Dfns wallet, we recommend authenticating the user yourself, and then calling delegated registration via a service account to register on behalf of the end user. This way, Dfns remains fully white labeled so your users will not know our platform exists.
User object
User id.
Required string length:
1 - 64Pattern:
^us-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$Example:
"us-6b58p-r53sr-rlrd3l5cj3uc4ome"
User kind.
Available options:
AccountUser, CustomerEmployee, EndUser Show child attributes
Show child attributes
Last modified on March 2, 2026
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.