Skip to content
Connection Guide

Connect Chargebee Without Breaking the Audit Trail

Use this guide to connect Chargebee or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryFinance
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Chargebee and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated read-only Chargebee API key and keep it scoped to the target site.
  2. 2
    Store base_url and api_key securely, and set business_entity_id only when entity-scoped collection is required.
  3. 3
    Validate Events plus the selected configuration endpoints before enabling scheduled sync.
  4. 4
    Keep governed write behavior disabled; this baseline is read-only only.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.