> 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/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>My API key isn't being accepted</summary>

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.

{% hint style="warning" %}
Make sure you're using a Circa API key and not a token from a connected third-party integration — these are different credentials.
{% endhint %}

</details>

<details>

<summary>The data flow fails immediately after I add the source</summary>

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.

</details>

## Missing data

<details>

<summary>My events aren't showing up in the output</summary>

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.

</details>

<details>

<summary>Custom field values aren't appearing in my data</summary>

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.

</details>

<details>

<summary>Event contacts or Company contacts show only IDs, no names</summary>

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.

</details>

## Permission errors

<details>

<summary>I get a 403 or "unauthorized" error when syncing</summary>

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.

</details>

## Data discrepancies

<details>

<summary>The contact count in Coupler.io doesn't match what I see in Circa</summary>

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.

</details>

## Rate limits

<details>

<summary>My data flow is failing or running slowly due to rate limits</summary>

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.

</details>


---

# 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/common-issues.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.