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

# Common Issues

## Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you copied the full API key from Breezy HR without any leading or trailing spaces. In Breezy HR, go to **Account Settings → Integrations → API** to find and regenerate your key if needed. If your key was recently regenerated, make sure you've updated it in Coupler.io as well.

</details>

<details>

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

This usually means your Breezy HR account has no records for the selected entity, or all positions are in a draft state not visible via the API. Check that the entity you selected (Positions, Candidates, or Pipelines) has at least one record in your Breezy HR account.

</details>

## Missing data

<details>

<summary>Some candidates are missing from my results</summary>

Candidates who were archived or deleted in Breezy HR may not appear in the export. Also confirm that the candidates are associated with an active or published position — candidates tied only to draft positions may not be returned.

</details>

<details>

<summary>Pipeline stages are missing or incomplete</summary>

Pipeline stages are configured per position in Breezy HR. If a position uses a non-default pipeline, the stages will reflect that position's custom setup. Make sure you're joining Pipelines data with the correct Position ID to get the right stages.

</details>

<details>

<summary>Candidate source field is blank</summary>

The source field is only populated when it was explicitly set during the application process or added manually in Breezy HR. Candidates added without a source attribution will have a blank value — this is expected behavior from the Breezy HR API.

</details>

## Permission errors

<details>

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

This means your API key is invalid or has been revoked. Regenerate your API key in **Breezy HR → Account Settings → Integrations → API**, then update the key in your Coupler.io data flow settings.

{% hint style="warning" %}
Only account owners and admins in Breezy HR can access and generate API keys. If you don't see the API section, ask your Breezy HR administrator.
{% endhint %}

</details>

## Data discrepancies

<details>

<summary>Candidate counts in Coupler.io don't match Breezy HR's dashboard</summary>

Breezy HR's dashboard may apply default filters (e.g., hiding disqualified candidates). The Coupler.io export pulls all candidate records available through the API, including disqualified ones. Filter by the Stage field in your destination to match what you see in Breezy HR.

</details>

<details>

<summary>A position shows as open in Breezy HR but closed in my export</summary>

This can happen if the position state was changed after your last data flow run. Run the data flow manually again to pull the latest status, or schedule more frequent syncs for time-sensitive reporting.

</details>

## Rate limits

<details>

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

Breezy HR's API has rate limits that can be hit when syncing large volumes of candidates or running multiple data flows simultaneously. Space out your data flows or reduce sync frequency if you hit this issue. If it persists, contact Breezy HR support to review your API usage limits.

</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/other/breezy-hr/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.