Salesforce introduced an additional permission requirement for SOAP API login() connections with the Winter ’27 release. If the Salesforce user connected to Soapbox Engage does not have this permission, you may see the following error in your Diagnostics View:
INSUFFICIENT_ACCESS: SOAP API login() requires the Use Any API Auth user permission.
If you see this message, the Salesforce user connected to Soapbox Engage needs the Use Any API Auth System Permission.
Why am I seeing this error?
As part of Salesforce Winter ’27, Salesforce requires users authenticating through SOAP API login() to have the Use Any API Auth permission.
Soapbox Engage uses SOAP API authentication for its current Salesforce integration. If the Salesforce user connected to Soapbox Engage does not have this permission, Salesforce will reject the authentication request.
This can affect an existing Soapbox Engage Salesforce connection, even if the connection was previously working successfully.
How can I resolve the error?
A Salesforce administrator can grant the required permission using a Permission Set.
In Salesforce:
- Navigate to Setup → Permission Sets.
- Select an existing Permission Set appropriate for your Soapbox Engage integration user, or create a new Permission Set.
- Select System Permissions.
- Click Edit.
- Locate Use Any API Auth and enable the permission.
- Click Save.
- Select Manage Assignments and assign the Permission Set to the Salesforce user connected to Soapbox Engage.
Once the permission has been assigned, return to Soapbox Engage and navigate to your Diagnostics View to confirm that your Salesforce credentials are working.
You should not need to reset your Salesforce password or security token, or re-enter your Salesforce credentials in Soapbox Engage.
Why is this important?
If Salesforce rejects the SOAP API authentication request, Soapbox Engage may be unable to create or update the corresponding records in Salesforce.
For example, a donation can successfully process through Soapbox Engage while the corresponding Salesforce records are not created because Salesforce authentication has failed.
If you encounter the error above, we recommend assigning the permission and confirming your connection through the Diagnostics View before processing additional transactions.
Still seeing the error?
If Use Any API Auth has been assigned to the Salesforce user and the error continues to appear, confirm that the Permission Set was assigned to the same Salesforce user whose credentials are entered in Soapbox Engage.
If the permission is assigned correctly and the Diagnostics View continues to report the error, please submit a ticket and include a screenshot of the error displayed in your Diagnostics View.