Common Issues

Connection issues

My API key isn't being accepted

Double-check that you've copied the full API key from your Circa account settings without any leading or trailing spaces. If the key still isn't accepted, try regenerating a new API key in Circa and entering that one instead.

Make sure you're using a Circa API key and not a token from a connected third-party integration — these are different credentials.

The data flow fails immediately after I add the source

This usually means the API key doesn't have sufficient permissions or has been revoked. Check your Circa account to confirm the key is still active. If you're on a restricted Circa plan, some entities may not be accessible via the API.

Missing data

My events aren't showing up in the output

Check the start date you set when configuring the source. If the start date is too recent, older events will be excluded. Use the date picker to move the start date further back to capture the full range of events you need.

Custom field values aren't appearing in my data

Custom field definitions live in the Event fields, Contact fields, and Company fields entities — but the actual values are stored within the Events, Contacts, and Companies entities. Make sure you're pulling the right entity for the values you need, not just the field definitions.

Event contacts or Company contacts show only IDs, no names

This is expected behavior. The relationship entities only store IDs. You need to use Coupler.io's Join transformation to combine Event contacts with the Contacts entity (matching on contact_id) to enrich the output with contact details.

Permission errors

I get a 403 or "unauthorized" error when syncing

This usually means the API key you're using doesn't have access to the entity you've selected. Some Circa plans restrict API access to certain data types. Check your Circa plan and confirm API access is enabled for your account.

Data discrepancies

The contact count in Coupler.io doesn't match what I see in Circa

This can happen if the start date filter is excluding older records. Try setting the start date further back to pull a fuller dataset. Also check whether any contacts in Circa were deleted — deleted records are typically not returned by the API.

Rate limits

My data flow is failing or running slowly due to rate limits

Circa's API has rate limits that may slow down or interrupt syncs for large datasets. If you hit rate limits, try reducing the number of entities in a single data flow or scheduling syncs during off-peak hours. Splitting large entity pulls across separate data flows can also help.