Connection Test Failures

Last updated: March 27, 2026

Symptoms

When setting up the Virtuous integration, clicking Test Connection fails. The integration won't connect or returns an authorization error.

Common Causes

Incorrect API Key. The most common cause. The API key entered in WeGive doesn't match what's configured in Virtuous, or it was copied with extra spaces or missing characters.

Wrong Default Communication ID. The Communication ID entered in WeGive doesn't match a valid communication in your Virtuous account.

Expired API Credentials. If your Virtuous API key was regenerated or revoked since it was originally entered in WeGive, the old key will no longer work.

Insufficient Permissions. The Virtuous user account associated with the API key may not have the necessary permissions to access the API.

How to Resolve

  1. Log into your Virtuous CRM admin settings and verify your API key. If you're unsure whether the key is current, generate a new one.

  2. Copy the API key carefully, making sure there are no leading or trailing spaces.

  3. In WeGive, go to Data > Integrations > Virtuous and paste the updated API key.

  4. Double-check your Default Communication ID in Virtuous and confirm it matches what's entered in WeGive.

  5. Click Test Connection again.

If the test still fails after verifying both values, confirm that your Virtuous user account has API access enabled. Contact your Virtuous administrator or Virtuous support if you're unsure about your account permissions.

If the connection was previously working and has stopped, your API key may have been regenerated by another admin. Check with your team to see if any changes were made to your Virtuous API settings.