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

# Common Issues

## Connection issues

<details>

<summary>My API key is rejected during setup</summary>

Double-check that you copied the full API key from Churnkey with no leading or trailing spaces. Churnkey API keys are typically found under account or developer settings — make sure you're using a key with read access, not a restricted or webhook-only key. If you recently rotated your key, the old one will no longer work and you'll need to paste the new one into your Coupler.io data flow settings.

</details>

<details>

<summary>The data flow connects but returns no data</summary>

This usually means the API key is valid but the associated account has no sessions recorded yet, or the key belongs to a sandbox/test environment with no activity. Confirm that your Churnkey account has at least one completed session. If you're using a test environment key, switch to your production key.

</details>

## Missing data

<details>

<summary>Some sessions are missing from the output</summary>

Churnkey only surfaces completed sessions through its API — sessions that were abandoned mid-flow or are still in progress may not appear. If you're seeing a gap for a specific date range, check whether those sessions were completed in Churnkey's own dashboard before assuming the data is missing from Coupler.io.

</details>

<details>

<summary>Session aggregations show different numbers than the Churnkey dashboard</summary>

Churnkey's dashboard may apply its own default filters (date range, plan type, etc.) that don't match what Coupler.io pulls. The API returns aggregations without those UI-level filters applied. Compare the raw totals by pulling the Sessions entity and aggregating manually to verify which view is correct for your use case.

</details>

## Permission errors

<details>

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

This means the API key doesn't have sufficient permissions. Some Churnkey plans restrict API access to certain tiers. Verify that your account plan includes API access and that the key you're using hasn't been revoked. Contact Churnkey support if you believe API access should be enabled on your plan.

</details>

## Data discrepancies

<details>

<summary>Revenue saved figures don't match my billing system</summary>

Churnkey records the MRR at the time the session occurs. If a customer subsequently upgraded, downgraded, or churned anyway after a grace period, Churnkey's revenue figure won't reflect that change. For reconciled revenue data, join Churnkey session records with your billing source (e.g., Stripe or Chargebee) in Coupler.io using the Join transformation.

</details>

## Rate limits

<details>

<summary>My data flow fails with a rate limit error</summary>

Churnkey's API has rate limits that apply per key. If you're running multiple data flows using the same API key simultaneously, you may hit these limits. Try staggering your data flow schedules or reducing the refresh frequency. If the problem persists, reach out to Churnkey to ask about rate limit thresholds for your plan.

</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/sales/churnkey/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.