FAQ

chevron-rightWhere do I find my Circa API key?hashtag

Log in to your Circa account and navigate to your account settings or developer settings. Your API key should be listed there. If you don't see it, check with your Circa account administrator — access to the API may depend on your plan or role.

chevron-rightCan I pull data from multiple Circa accounts into one destination?hashtag

Yes. You can add multiple Circa sources to a single data flow — one per account — and use Coupler.io's Append transformation to combine the data into one output table. This is useful if your organization manages events across separate Circa workspaces.

chevron-rightWhich entities should I use to build an attendee report?hashtag

Start with the Events entity to get event details, then add Event contacts to get the event-to-contact relationships, and finally add Contacts for the actual contact information. Use Coupler.io's Join transformation to link these entities on their shared IDs.

chevron-rightWhat does the start date parameter do?hashtag

The start date controls how far back in time Coupler.io pulls records from Circa. Records created or updated before the start date won't be included in your data flow output. Use the date picker in the source settings to adjust this range.

chevron-rightCan I use Circa data with AI tools?hashtag

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send your Circa event or contact data directly to these tools for analysis, summarization, or generating insights from your event CRM data.

chevron-rightWhy do my Company contacts and Event contacts only show numbers, not names?hashtag

These are relationship entities — they store IDs that link records together, not the actual contact details. To get readable output, use the Join transformation to connect these entities with the Contacts table on the contact_id field. See the Data Overview for recommended entity combinations.

chevron-rightHow often can I refresh Circa data?hashtag

This depends on Circa's API rate limits and your Coupler.io plan. For most use cases, hourly or daily refreshes work well. If you're pulling many entities at once and hitting rate limits, try splitting them across separate data flows or reducing refresh frequency.

circle-info

For details on available fields and recommended entity combinations, see Data Overview. For sync errors and permission problems, check Common Issues. For setup tips specific to Circa, visit Best Practices.

Last updated

Was this helpful?