> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/circa/faq.md).

# FAQ

<details>

<summary>Where do I find my Circa API key?</summary>

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.

</details>

<details>

<summary>Can I pull data from multiple Circa accounts into one destination?</summary>

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.

</details>

<details>

<summary>Which entities should I use to build an attendee report?</summary>

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.

</details>

<details>

<summary>What does the start date parameter do?</summary>

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.

</details>

<details>

<summary>Can I use Circa data with AI tools?</summary>

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.

</details>

<details>

<summary>Why do my Company contacts and Event contacts only show numbers, not names?</summary>

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.

</details>

<details>

<summary>How often can I refresh Circa data?</summary>

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.

</details>

{% hint style="info" %}
For details on available fields and recommended entity combinations, see [Data Overview](/sources/category/crm/circa/data-overview.md). For sync errors and permission problems, check [Common Issues](/sources/category/crm/circa/common-issues.md). For setup tips specific to Circa, visit [Best Practices](/sources/category/crm/circa/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/crm/circa/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.