This issue occurs when a user attempts to run an Apsona button and Salesforce blocks the action due to missing system-level API access. Although Apsona uses permission sets for feature access, the execution of Apsona buttons relies on the Salesforce API.
When the API Enabled permission is missing from the user profile or permission set, Salesforce returns the following error message:
API_CURRENTLY_DISABLED: API is disabled for this User
This behavior may appear confusing because:
System Administrators can run the button successfully even without Apsona permission sets, since admin profiles automatically include API access
Standard users with Apsona permission sets may still fail if API access is disabled
Apsona permission sets such as Apsona Allow Filters Option do not control API access or button execution
How to resolve the issue:
Enable Salesforce API access for the affected user by adjusting either:
Their Profile, or
The relevant Permission Set
Navigate to:
Setup → Profile or Permission Set → System Permissions → Enable “API Enabled”
Once the API Enabled permission is applied, the user can run the Apsona button without error.
Key takeaway:
This error is unrelated to Apsona licensing or feature permission sets—Apsona merge buttons require the Salesforce API Enabled permission to run, and failure occurs only when Salesforce blocks API activity for the user.