Common Issues

Connection issues

My API key is not being accepted

Double-check that you've copied the full API key from your BlueTally account settings — partial keys are a common cause of auth failures. Make sure there are no leading or trailing spaces when pasting the key into Coupler.io. If the key was recently regenerated in BlueTally, you'll need to update it in your Coupler.io data flow as well.

The data flow fails immediately after I save it

This usually means the API key is invalid or has been revoked. Go to BlueTally account settings, verify the key is active, and re-enter it in Coupler.io. If your BlueTally account has been suspended or downgraded, API access may have been disabled.

Missing data

Some assets are not showing up in my export

Check the start date you set in the data flow configuration. If the start date is too recent, assets created or updated before that date will be excluded. Use the date picker to extend the range further back. Also confirm that those assets are not archived or deleted in BlueTally — archived records may not be returned by the API.

The Employees entity returns fewer records than expected

BlueTally may only return employees who have at least one asset assigned or who are marked as active. Offboarded employees with no active assignments may not appear. Check your BlueTally account directly to confirm which employee records are visible via the API.

Permission errors

I get a "forbidden" or "unauthorized" error

Your API key may not have sufficient permissions to read Assets or Employees data. In BlueTally, check whether your account role allows API access. Some plans or user roles restrict API usage — contact your BlueTally account admin to confirm.

Data discrepancies

Asset counts in Coupler.io don't match what I see in BlueTally

This is almost always caused by the start date filter. Coupler.io only pulls records from the date you specified onward. Set the start date as far back as needed, re-run the data flow, and compare again. Also check whether any assets have been deleted in BlueTally — deleted records are typically not returned by the API.

Category or status values look inconsistent in my destination

BlueTally passes through whatever values are stored in your account — there's no normalization. If your team has used inconsistent naming (e.g., "Laptop" vs. "laptop" vs. "Laptops"), those variations will appear in the export. Clean these up directly in BlueTally for consistent reporting.