Skip to main content
API tokens in Dynamic are scoped to specific resources and actions, ensuring that each token only has the minimum permissions necessary for its intended use case. This follows the principle of least privilege, enhancing security by limiting access to only what’s required. When creating an API token, you can select from the following permission scopes, organized by resource type:

WaaS (Wallet as a Service) Permissions

waas.authenticate

Description: Authenticate with WaaS (Wallet as a Service) for wallet operations.

waas.delegatedAccess.signMessage

Description: Sign messages on behalf of users through delegated wallet access.

Environment Permissions

environment.balances.read

Description: Read user balance information across multiple chains.

environment.apiTokens.read

Description: Read environment API token information.

environment.apiTokens.write

Description: Create and manage environment API tokens.

environment.events.read

Description: Read event data and event types for the environment.

environment.webhooks.read

Description: Read webhook configurations and message history.

environment.webhooks.write

Description: Create, update, and manage webhook configurations.

environment.analytics.read

Description: Read analytics data including visits, wallets, and engagement metrics.

environment.users.read

Description: Read user data, wallets, and related information.

environment.users.write

Description: Create, update, and manage users, wallets, and user-related data.

environment.settings.read

Description: Read environment configuration settings including global wallets, custom fields, gates, providers, and more.

environment.settings.write

Description: Create, update, and manage environment configuration settings including global wallets, custom fields, gates, providers, and more.
Last modified on May 27, 2026