> 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.md).

# Bunny, Inc.

Connect Bunny, Inc. billing data to Google Sheets or BigQuery. Pull invoices, subscriptions, payments, and account records via Coupler.io.

Bunny, Inc. is a billing and subscription management platform designed for businesses that handle recurring revenue, invoicing, and customer account management. It brings together accounts, subscriptions, payments, and financial transactions in one place. By connecting Bunny, Inc. to Coupler.io, you can pull all that financial data into your reporting and analytics tools without any manual exports.

## Why connect Bunny, Inc. to Coupler.io?

* **Centralize your billing data** — combine accounts, invoices, payments, and subscriptions into a single destination for reporting
* **Automate revenue reporting** — keep dashboards in Google Sheets, Looker Studio, or BigQuery refreshed automatically on a schedule
* **Unlock AI-powered analysis** — send your financial data to ChatGPT, Claude, or Gemini to summarize trends, flag anomalies, or generate insights
* **Join entities for richer context** — link invoices with invoice items, or subscriptions with subscription charges, using Coupler.io's Join transformation

## Prerequisites

Before you connect, make sure you have:

* A Bunny, Inc. account with access to the data you want to export
* A Bunny, Inc. API key (found in your account settings or developer/API section)
* A Coupler.io account (free plan works to get started)

## Quick start

{% hint style="success" %}
If you're building a revenue dashboard, start with **Invoices** and **Payments** as your first sources. Use Coupler.io's Join transformation to match invoice line items to their parent invoices for a complete billing picture.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account, go to the Data Flows section, and click **Add data flow**.
{% endstep %}

{% step %}
**Select Bunny, Inc. as your source.** Search for "Bunny, Inc." in the source list and select it.
{% endstep %}

{% step %}
**Enter your API key.** Paste your Bunny, Inc. API key into the API key field. You can find this in the API or developer settings section of your Bunny, Inc. account.
{% endstep %}

{% step %}
**Choose an entity.** Select which data you want to pull — for example, Invoices, Payments, Subscriptions, or any of the other available entities.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to specify how far back you want to pull historical data.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual run and verify your data is pulling correctly.
{% endstep %}
{% endstepper %}

## Bunny, Inc. data overview

Bunny, Inc. exposes a broad set of financial and billing data through Coupler.io. You can pull everything from high-level account and subscription data to granular invoice line items and individual transaction records.

## Available entities

| Entity               | What it contains                                                              |
| -------------------- | ----------------------------------------------------------------------------- |
| Accounts             | Customer account records including status, contact links, and billing details |
| Account balances     | Current and historical balance per account                                    |
| Contacts             | Names, emails, and other contact details for customers and prospects          |
| Entities             | Business entity configurations used in your Bunny setup                       |
| Invoices             | Invoice headers including totals, dates, status, and linked accounts          |
| Invoice items        | Line-level detail for each invoice — product, quantity, price                 |
| Payments             | Individual payment records with amounts, dates, and status                    |
| Products             | Product and service catalog with pricing info                                 |
| Plans                | Subscription plan definitions and pricing tiers                               |
| Quotes               | Quote headers with totals and customer links                                  |
| Quote charges        | Line items within quotes                                                      |
| Subscriptions        | Subscription records — active, cancelled, and historical                      |
| Subscription charges | Recurring charge records tied to subscriptions                                |
| Transactions         | Raw financial transaction and payment processing records                      |
| Tenants              | Multi-tenant configuration data                                               |

## Key fields by entity

#### Accounts

| Field        | Description                               |
| ------------ | ----------------------------------------- |
| Account ID   | Unique identifier for the account         |
| Account name | Name of the customer or business          |
| Status       | Active, inactive, or other account states |
| Created date | When the account was created              |
| Balance      | Current account balance                   |

#### Invoices & Invoice items

| Field            | Description                           |
| ---------------- | ------------------------------------- |
| Invoice ID       | Unique invoice identifier             |
| Account ID       | Linked customer account               |
| Invoice date     | Date the invoice was generated        |
| Due date         | Payment due date                      |
| Total amount     | Total billed amount                   |
| Status           | Draft, issued, paid, overdue, etc.    |
| Item description | Line item description (Invoice items) |
| Unit price       | Price per unit (Invoice items)        |
| Quantity         | Number of units (Invoice items)       |

#### Payments & Transactions

| Field          | Description                            |
| -------------- | -------------------------------------- |
| Payment ID     | Unique payment identifier              |
| Account ID     | Linked customer account                |
| Amount         | Payment amount                         |
| Payment date   | Date payment was received or processed |
| Status         | Successful, failed, pending, etc.      |
| Transaction ID | Raw transaction reference              |
| Payment method | How the payment was made               |

#### Subscriptions & Subscription charges

| Field           | Description                                    |
| --------------- | ---------------------------------------------- |
| Subscription ID | Unique subscription identifier                 |
| Plan ID         | Linked plan                                    |
| Account ID      | Linked customer account                        |
| Start date      | Subscription start date                        |
| End date        | Subscription end date or cancellation date     |
| Status          | Active, cancelled, paused, etc.                |
| Charge amount   | Amount billed per cycle (Subscription charges) |
| Billing cycle   | Frequency of billing (Subscription charges)    |

#### Plans & Products

| Field                | Description                   |
| -------------------- | ----------------------------- |
| Plan ID / Product ID | Unique identifier             |
| Name                 | Plan or product name          |
| Price                | List price                    |
| Billing interval     | Monthly, annual, etc. (Plans) |
| Description          | Product or plan description   |

#### Quotes & Quote charges

| Field              | Description                            |
| ------------------ | -------------------------------------- |
| Quote ID           | Unique quote identifier                |
| Account ID         | Linked customer account                |
| Total amount       | Total quoted amount                    |
| Status             | Draft, sent, accepted, expired, etc.   |
| Charge description | Line item detail (Quote charges)       |
| Charge amount      | Amount per charge line (Quote charges) |

## Common entity combinations

* **Invoices + Invoice items** — Join these to get full invoice detail with line-level breakdown. Useful for revenue attribution by product.
* **Subscriptions + Subscription charges** — Join to see exactly what each subscriber is being billed and when.
* **Accounts + Account balances** — Join for a complete customer financial health view.
* **Payments + Transactions** — Append or join to reconcile payment records against raw transaction data.
* **Plans + Subscriptions** — Join to analyze which plans are most popular and generating the most revenue.

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* **Revenue reconciliation** — Pull Invoices, Payments, and Transactions into BigQuery or Google Sheets to reconcile billed vs. collected revenue
* **Accounts receivable tracking** — Use Account balances and Invoices to monitor outstanding balances and overdue accounts
* **MRR/ARR reporting** — Combine Subscriptions and Subscription charges to calculate monthly and annual recurring revenue over time
  {% endtab %}

{% tab title="Sales ops" %}

* **Quote-to-close tracking** — Pull Quotes and Quote charges to monitor conversion rates and average deal size
* **Account health overview** — Join Accounts and Account balances to spot at-risk customers with declining balances or overdue invoices
* **Product performance** — Link Invoice items and Products to see which products are driving the most revenue
  {% endtab %}

{% tab title="Operations" %}

* **Subscription lifecycle management** — Track active, paused, and cancelled subscriptions over time to understand churn patterns
* **Multi-tenant reporting** — Use the Tenants entity to segment financial data by tenant in multi-tenant deployments
* **Billing anomaly detection** — Send Transactions or Payments data to Claude or ChatGPT to flag unusual patterns automatically
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **start date** parameter controls how far back historical data is pulled — set this carefully on first run if you have a long account history
* **Account balances** are a snapshot entity — they reflect current state, not a historical ledger, so schedule frequent refreshes if you need balance trend data
* **Tenants** is only relevant for multi-tenant Bunny configurations; skip it if you operate a single-tenant setup
* Entities like **Contacts** and **Entities** are relatively static — you don't need to refresh these as frequently as Payments or Transactions

## Bunny, Inc. common issues

### Connection issues

<details>

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

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.

</details>

<details>

<summary>The data flow fails immediately after I enter my API key</summary>

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.

</details>

### Missing data

<details>

<summary>My data only goes back a short time — I expected more history</summary>

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.

</details>

<details>

<summary>Some invoices or payments are missing from the export</summary>

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.

</details>

<details>

<summary>The Tenants entity returns no data</summary>

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.

</details>

### Permission errors

<details>

<summary>I get a "403 Forbidden" or "Unauthorized" error</summary>

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.

</details>

### Data discrepancies

<details>

<summary>The totals in Coupler.io don't match what I see in Bunny, Inc.</summary>

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.

</details>

<details>

<summary>Account balances look outdated</summary>

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.

</details>

### Rate limits

<details>

<summary>My data flow is timing out or returning partial data</summary>

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.

</details>

## Bunny, Inc. FAQ

<details>

<summary>What is Bunny, Inc. and what kind of data can I export?</summary>

Bunny, Inc. is a billing and subscription management platform. Through Coupler.io, you can export 15 entities including Accounts, Invoices, Payments, Subscriptions, Transactions, Plans, Products, Quotes, and more. This covers the full billing lifecycle from quoting to payment collection.

</details>

<details>

<summary>Where do I find my Bunny, Inc. API key?</summary>

Log in to your Bunny, Inc. account and navigate to the API or developer settings section. There you'll find your API key or an option to generate one. Copy the full key and paste it into the Coupler.io source configuration.

</details>

<details>

<summary>Can I connect multiple Bunny, Inc. accounts?</summary>

Yes. Create a separate source in Coupler.io for each account using the respective API key. Then use Coupler.io's **Append** transformation to combine data from all accounts into a single destination for unified reporting.

</details>

<details>

<summary>What's the difference between Payments, Transactions, and Invoice items?</summary>

* **Payments** — records of money received from customers against invoices
* **Transactions** — raw payment processing records at the gateway level
* **Invoice items** — the line-level breakdown of what was billed on an invoice (products, quantities, prices)

These are complementary, not interchangeable. For reconciliation, use all three together.

</details>

<details>

<summary>Can I combine Invoices with Invoice items in one report?</summary>

Yes — use Coupler.io's **Join** transformation to link Invoice items to their parent Invoices using the Invoice ID field. This gives you a single table with both header-level totals and line-level product detail.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

Coupler.io uses the **start date** parameter to control how far back data is fetched. Use the date picker to set your desired start date. There's no hard limit on how far back you can go, but very large historical datasets (e.g., years of Transactions) may take longer to load on the first run.

</details>

<details>

<summary>Can I send Bunny, Inc. data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your billing or subscription data directly to these tools for analysis, summarization, or anomaly detection without any manual export.

</details>

<details>

<summary>Why does the Tenants entity return no data?</summary>

The Tenants entity only contains data if your Bunny, Inc. account is configured for multi-tenant use. Single-tenant accounts will see an empty result — this is expected. You can safely skip this entity if it doesn't apply to your setup.

</details>

<details>

<summary>Do I need to re-enter my API key if I regenerate it in Bunny, Inc.?</summary>

Yes. If you regenerate your API key in Bunny, Inc., you'll need to update it in your Coupler.io data flow as well. The old key will stop working immediately, which will cause your data flow to fail until the new key is entered.

</details>

{% hint style="info" %}
For help understanding which entities to use for specific reports, see the [Data Overview](#bunny-inc-data-overview) article. If your data flow is failing or returning unexpected results, check [Common Issues](#bunny-inc-common-issues) for troubleshooting steps.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/bunny-inc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
