Overview
Redbark is an Australian Consumer Data Right (CDR) Representative of Fiskil — an ACCC-accredited data recipient. Connecting a bank through Redbark is the regulated, read-only equivalent of giving Beeswax a permission slip to fetch transactions on your behalf, without ever sharing your banking password.
| Aspect | Detail |
|---|---|
| Regions | Australia |
| Connection style | Paste a Redbark API key once; Beeswax discovers all your connected accounts |
| What gets imported | Transactions, balances, account details — read-only |
| Sync cadence | Every 4 hours, with a 14-day sliding window so late-posting transactions still get picked up |
| Consent maximum | 12 months from when you authorise Redbark — you'll need to renew with them after that |
Already using Revolut? Bank Feed Setup covers that integration. You can run Revolut and Redbark side by side, but each Beeswax bank account can only have one external feed connected at a time.
Before You Start
- A Redbark Developer account. Sign up at redbark.co and subscribe to the Developer tier.
- At least one bank connected inside Redbark. Their dashboard handles the per-bank consent step. Beeswax doesn't see this step at all — it just consumes the API key once you're set up.
- Beeswax bank accounts ready to receive feeds. You'll need an Asset-type transaction account marked as a bank account for each Redbark account you want to sync. Create them under Chart of Accounts before continuing.
- The right permissions in Beeswax. Owners, Super Admins, and Accountants can connect bank feeds.
Setup
1. Generate a Redbark API key
In your Redbark dashboard, go to Developer → API Keys and create a new key. Keys look like rbk_live_…. Copy it once — Redbark won't show it again.
2. Paste the key into Beeswax
In Beeswax, go to Settings → Bank Feeds, find the Redbark card, and click Connect Redbark. Paste your key and click Test and save. Beeswax validates the key against Redbark and stores it encrypted at rest. If the key is rejected, you'll see a clear error and nothing is saved.
3. Map your Redbark accounts to Beeswax bank accounts
After a successful connect, Beeswax opens the Account Mapping page. For every account Redbark sees on your behalf, pick which Beeswax bank account it should feed into — or leave it blank to skip syncing that one.
A Beeswax account that's already attached to a different feed (e.g. Revolut) appears greyed out. Disconnect there first if you want to switch providers.
Click Save mappings. Beeswax creates the per-account links and is now ready to sync.
4. (Optional) Backfill historical transactions
By default, Beeswax syncs the last 90 days when you first connect. If you want to pull more history — up to the 12-month CDR limit — click Backfill history on the Redbark card, pick a start date, and submit. Beeswax queues the work in 90-day chunks under the hood. Backfill is idempotent — you can run it as many times as you like without creating duplicate transactions.
How Sync Works
- Scheduled: every 4 hours, Beeswax pulls the last 14 days of transactions for every mapped account. The 14-day window catches transactions that post late at the bank.
- On demand: click Sync now on the Redbark card to trigger the same job out of cycle.
- Backfill: the Backfill history button pulls older data, broken into 90-day chunks.
Every sync — scheduled, on-demand, or backfill — is recorded on the Redbark card under Recent activity with a status, timestamp, and the count of new transactions imported.
Connection Health
The Redbark card on the Bank Feeds page shows:
- Status pill — Active / Reconnect required / Not connected
- Last polled — when Beeswax last contacted Redbark
- Last clean sync — most recent successful poll, with the count of transactions imported then
- Mapped accounts — how many bank accounts are currently set to sync
- Recent activity — the last 5 polls, with status and outcome
- Consent expiry countdown (when available) — coloured info → warning → danger as your CDR consent approaches its 12-month expiry
If the card turns red and the page shows a Reconnect required banner, it usually means your Redbark API key has been revoked or rotated. Click Reconnect Redbark, paste a fresh key, and your feeds resume.
Switching Providers or Disconnecting
Each Beeswax bank account can have only one external feed at a time. To switch a bank account from Revolut to Redbark (or vice versa), disconnect the existing feed first.
Disconnecting Redbark:
- Removes the API key from Beeswax.
- Removes all per-account mappings under it.
- Keeps every transaction Beeswax has already imported — those belong to your bank account ledger, not the feed.
Reconnecting later goes through the same paste-key + map-accounts flow.
Troubleshooting
"That API key was rejected by Redbark."
The key is invalid, revoked, or rotated. Copy a fresh one from your Redbark dashboard and paste it again.
"Reconnect required" banner.
Same cause as above. Click Reconnect Redbark on the card and paste a current key.
Transaction count looks low after a sync.
Banks post some transactions late. The 14-day rolling re-sync should catch them on the next scheduled run. If you suspect a transaction is genuinely missing after several days, contact support.
A Beeswax account is greyed out in the mapping dropdown.
It's already connected to another feed (commonly Revolut). Disconnect that first.
"Couldn't reach Redbark."
Transient network issue or a Redbark outage. Beeswax retries automatically with exponential backoff; the next scheduled run will pick up from where the failed one left off.