> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Campfire

> Monk integration with Campfire revenue and contract management

# Campfire

Monk connects to Campfire over HTTPS using a direct API key. The integration
keeps customer, invoice, payment, and credit-memo data in sync for a single
Campfire chart entity per Monk organization.

## Supported entities

| Monk entity       | Campfire entity   |
| ----------------- | ----------------- |
| Customer          | Customer / vendor |
| Customer contacts | Contact           |
| Invoice           | Invoice           |
| Invoice line      | Invoice line      |
| Payment           | Invoice payment   |
| Credit memo       | Credit memo       |
| Product / item    | Product           |
| Chart of accounts | Account           |
| Chart entity      | Chart entity      |

## Authentication

* Create an API key in **Campfire Settings → API** and paste it into Monk.
* Monk sends the key as `Authorization: Token <key>` on every request.
* Campfire does not support OAuth; API keys can be rotated in Campfire and
  updated in Monk at any time.

## Multi-entity, currency, and parent-child

* **Chart entity:** One Monk org maps to one Campfire chart entity. Invoices,
  payments, and credit memos are read from that entity; customers and products
  may be organization-wide.
* **Currency:** Invoice and payment amounts retain their original ISO currency.
  Campfire records an exchange rate on transactions, and Monk preserves it.
* **Customer hierarchy:** Parent/child customer relationships exposed by Campfire
  are preserved in Monk.

## Configuration options

* **Payment account:** choose the Campfire GL account used for payment
  transactions.
* **Historical cutover date:** limit how far back Monk imports invoices and
  payments.
* **Auto-import:** enable or disable automatic import of new Campfire invoices
  and customers.

## Sync and reliability

* Incremental sync using `last_modified_at` timestamps for most entities.
* Payment feeds support opaque cursor paging for large transaction histories.
* Voided payments and credit-memo applications are reconciled from the feed and
  restore invoice balances.
* Product records are periodically reconciled because their modification
  timestamps may be absent.

## Frequently asked questions

**Do I need an OAuth app for Campfire?**
No. Campfire uses static API keys. Generate one in Campfire and provide it to
Monk.

**Can one Monk org sync more than one Campfire chart entity?**
One Monk org connects to one chart entity. Connect additional Monk orgs for
additional entities and use Monk's org hierarchy for roll-up.

**How are Stripe and manual payments handled?**
Campfire payment records carry a `payment_type` and `source`. Monk imports all
payment types that appear in the invoice-payments feed and applies them to the
matching invoice.