Common Bloomerang Integration Issues

Last updated: March 28, 2026

This article covers the most common issues you may encounter with the Bloomerang integration and how to resolve them.

Connection Test Failures

Symptoms: The integration won't connect, or you see a "Bloomerang connection failure" message.

Common causes and fixes:

  • Incorrect API key. Verify the key was copied correctly from Bloomerang with no extra spaces. Make sure it was generated from the API Keys v2.0 section (Settings > Users), not an older API version.

  • Expired or revoked key. If another admin regenerated the API key in Bloomerang, the old key will no longer work. Generate a new one and update it in WeGive.

  • Insufficient permissions. The Bloomerang user account that generated the API key must have full administrative permissions.

  • Billing issues. If the Bloomerang account has billing problems, the API may be disabled. Check with your Bloomerang account owner.

Missing or Incorrect Default Fund ID

Symptoms: The integration connects successfully, but all transaction syncs fail. You see errors related to Fund ID in your Integration Logs.

Cause: Bloomerang requires every transaction to have a Fund ID. If the Default Fund ID is missing or incorrect in your WeGive integration settings, no transactions can sync.

How to fix:

  1. In Bloomerang, go to Settings > Custom Data > Funds

  2. Find the fund marked as "Default"

  3. Click on it and copy the ID from the URL

  4. In WeGive, go to Data > Integrations > Bloomerang

  5. Paste the correct Fund ID and save

Clear any integration locks after updating the Fund ID. WeGive will retry the failed transactions on the next sync cycle.

Slow Initial Sync

Symptoms: The initial sync has been running for over an hour and doesn't seem to be finishing.

This is expected behavior. Bloomerang's API is limited to 20 records per request. For organizations with thousands of records, the initial sync can take well over 60 minutes. This is a Bloomerang API limitation, not a WeGive issue.

What to do:

  • Let the sync run. You do not need to stay on the page.

  • Monitor progress at Data > Integration Logs to confirm records are still being processed.

  • If the sync appears completely stuck (no new log entries for 30+ minutes), try clicking Begin Sync again.

After the initial sync completes, ongoing syncs only process recent changes and are much faster.

Environment Mismatch

Symptoms: Connection fails even though the API key and Fund ID are correct.

Cause: WeGive enforces strict environment matching. Test WeGive accounts (marked with "[TEST]") can only connect to Bloomerang Sandbox instances. Production WeGive accounts can only connect to production Bloomerang instances.

How to fix: Check which WeGive account you're logged into (look for "[TEST]" in the top right corner). Make sure you're connecting to the matching Bloomerang environment.

Records Failing to Sync

Symptoms: Specific records are stuck in Integration Locks or showing errors in Integration Logs.

How to diagnose:

  1. Go to Data > Integration Locks to see which records are stuck

  2. Review the error message on each locked record

  3. Check Data > Integration Logs for more detail on the failure

Common causes:

  • Missing required fields in Bloomerang (e.g., a transaction without a valid constituent match)

  • Data format mismatches between the two systems

  • API permission changes in Bloomerang

How to fix: Address the underlying issue described in the error message, then archive the lock at Data > Integration Locks. WeGive will retry the sync within 15 minutes.

Data Not Appearing Immediately

Symptoms: A change was made in Bloomerang but it hasn't shown up in WeGive yet.

This is expected. Bloomerang to WeGive syncs run every 15 minutes. Changes made in Bloomerang may take up to 15 minutes to appear in WeGive. If you need the data sooner, trigger a manual sync from your integration settings.

Changes made in WeGive should appear in Bloomerang immediately (real-time push).

When to Contact Support

Reach out to WeGive support if:

  • Your API key appears correct but the connection still fails after verifying all settings

  • Integration Logs show persistent errors that don't match any of the issues above

  • The sync has been running for over 2 hours with no progress visible in the logs

  • You need help identifying or resolving data conflicts between the two systems