Common Issues

Connection issues

My API key is not being accepted

Double-check that you copied the full API key from Aha without any trailing spaces. You can find your API key in Aha under Profile settings > Developer > API key. If the key has been regenerated recently, make sure you're using the latest version. Also, confirm that your Aha account has API access enabled — some lower-tier plans may restrict this.

I'm getting a "domain not found" or "invalid domain" error

Make sure you're entering only the subdomain portion of your Aha URL. For example, if your workspace is at yourcompany.aha.io, enter yourcompany — not the full URL. Including https:// or .aha.io in the domain field will cause the connection to fail.

Missing data

Some features or ideas aren't showing up in my export

Aha may not return archived or deleted records through the API. Check whether the missing items have been archived in your Aha workspace. Also, verify that the records belong to the product or workspace your API key has access to — if your key is scoped to a specific workspace, records outside that scope won't appear.

Idea endorsements or comments are empty even though I can see them in Aha

Endorsements and comments are separate entities in Coupler.io — they won't appear in the Ideas stream. Make sure you've set up separate sources for Idea endorsements streams and Idea comments streams if you need that data.

Permission errors

I'm getting a 403 or "unauthorized" error

This usually means the API key doesn't have sufficient permissions to access the requested data. Make sure the Aha user account associated with the API key has the appropriate role in the workspace. Admin or product owner roles typically have the broadest API access. If you're on a team plan, check with your Aha administrator to confirm API access is enabled for your account.

Data discrepancies

The feature count in Coupler.io doesn't match what I see in Aha

This can happen if your Aha view is filtered (e.g., by release, assignee, or status) while the API returns all records. Check whether any filters are applied in your Aha workspace view that wouldn't apply to the API. Also, confirm you're looking at the same product — if you have multiple products, the API will return features across all of them.

Description fields contain HTML tags instead of plain text

Aha stores rich text descriptions with HTML formatting. This is expected behavior — the API returns the raw HTML. If you need plain text, you'll need to strip the HTML tags after export using a formula or data transformations in your destination tool.

Rate limits

My import is failing or timing out for large workspaces

Aha enforces API rate limits that can slow down or interrupt large data pulls. If you have a large workspace with thousands of features or ideas, try scheduling your data flows during off-peak hours. If the issue persists, consider splitting your imports across multiple data flows by entity type to reduce the load per sync.