> 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/finance-and-accounting/bunny-inc/common-issues.md).
# Common Issues
## Connection issues
My API key is not being accepted
Double-check that you're copying the full API key from Bunny, Inc. — no extra spaces at the start or end. Make sure you're using an API key with read access to the entities you're trying to pull. If the key was recently regenerated in your Bunny account, you'll need to update it in Coupler.io as well.
The data flow fails immediately after I enter my API key
This usually means the API key doesn't have permission to access the selected entity, or the key has been deactivated. Try generating a new API key in Bunny, Inc. and reconnecting. If the issue persists, check whether your Bunny, Inc. plan includes API access.
## Missing data
My data only goes back a short time — I expected more history
Check the **start date** you set when configuring the source. If you set a recent date, Coupler.io will only pull data from that point forward. Edit the data flow and use the date picker to set an earlier start date, then run it again.
Some invoices or payments are missing from the export
Bunny, Inc. may filter records based on status. Draft invoices or pending payments might not appear in certain entity exports depending on how the Bunny API returns data. Try pulling both the **Invoices** and **Transactions** entities and cross-referencing them to find missing records.
The Tenants entity returns no data
The Tenants entity only returns data if your Bunny, Inc. account is configured for multi-tenant use. If you're on a single-tenant setup, this entity will return empty results — that's expected behavior.
## Permission errors
I get a "403 Forbidden" or "Unauthorized" error
This means your API key doesn't have permission to access the requested entity. Log in to Bunny, Inc. and check the permissions scope assigned to your API key. Some entities — like Tenants or Entities — may require elevated access rights.
## Data discrepancies
The totals in Coupler.io don't match what I see in Bunny, Inc.
Make sure your start date in Coupler.io covers the same period you're comparing against in Bunny, Inc. Also check whether you're looking at the **Invoices** total vs. the **Payments** total — these represent different things (billed vs. collected). For a full reconciliation, pull both entities and compare them side by side.
Account balances look outdated
Account balances reflect a point-in-time snapshot from when the data flow last ran. If you need up-to-date balances, increase your refresh frequency in the schedule settings. Remember: you need a successful manual run before you can set up a schedule.
## Rate limits
My data flow is timing out or returning partial data
If you have a large volume of records (e.g., many years of transactions), the initial pull can take a long time. Try setting a more recent start date for the first run to get a smaller dataset, then gradually move the start date earlier in subsequent runs. For very large datasets, consider splitting entities into separate data flows.
---
# 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/finance-and-accounting/bunny-inc/common-issues.md?ask=&goal=
```
`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.