The weekly cadence slipped, so this is a single catch-up covering May. June follows in the next entry.

The MCP server now supports OAuth. You can connect Redbark to Claude or any other MCP client by signing in through the browser, instead of pasting an API key into a config file. Connected apps are listed in your settings, and you can revoke any of them whenever you want.

I put the API and MCP server through an OWASP API Top 10 audit and fixed everything it turned up, along with the findings from an external penetration test. Alongside that, a batch of correctness work on the API: brokerage endpoints now validate properly and return a clear 400 instead of a confusing error, validation errors all share one shape, and upstream bank failures surface as real errors rather than being quietly swallowed or cached as empty.

A few classes of breakage now recover without you touching anything. When a bank regenerates its internal account IDs, Redbark re-matches your accounts instead of stalling. If you repoint an account mapping at a different destination, it backfills automatically. Brokerage connections repair their own end-user mapping if it goes missing. And when you revoke consent at your bank, the connection is now cleaned up properly on both sides.

Late in the month the document extractor went into beta. Upload a PDF statement or a receipt, or forward it to your own Redbark inbound address, and the transactions get pulled out and synced to your destination like any other transaction. Useful for the accounts Open Banking doesn't reach.

YNAB syncs now skip transactions older than YNAB's own five-year window instead of erroring on them, trial users have API access again, and the dashboard sidebar is grouped into sections so it stays readable as the product grows.

Last week's work, and a big one.

Connect Redbark to Claude with MCP

Redbark now runs an MCP server, which means you can plug it into Claude (or any MCP client) and ask questions of your transactions, balances, holdings, and trades directly from a conversation. "How much did I spend on groceries last month?" works without you ever opening a spreadsheet. Available on the Developer plan and up. Full docs on the MCP page.

Give a month, get a month

Referrals are live. Share your referral link, and when someone you refer subscribes, you both get a month free. Grab your link from the billing page.

Clearer consent and destination setup

When you set up a destination now, there's a short acknowledgement of exactly what banking data is about to leave Redbark and where it's going, so there are no surprises about what's being shared. Consent screens also show clearer disclosures about which parts of your data each destination receives. There's a new public FAQ covering this end-to-end if you want the long version.

Brokerage trades via webhook

If you're on a webhook destination and you sync a brokerage, your trade history now flows through alongside your transactions. Same payload shape, same signing.

Smaller improvements

Transaction categories automatically flow through to older syncs so you get full categorisation without any manual work, and if a destination disconnects, the sync pauses itself and lets you know so you can fix it when you're ready.

Two headline items this week.

NZ banking with Akahu is on the way

New Zealand is the next country on the list. The Akahu integration is in place behind the scenes and I'll be opening it up to early testers shortly. If you're in New Zealand and want in, reply to any Redbark email and I'll add you to the list.

Optional pending transactions

Pending transactions now sync if you opt in on a per-sync basis. It's experimental (pending data is inherently messy and shifts around before it posts), but if you want the earliest visibility into what you've just spent, you can turn it on.

Smaller improvements

Brokerage connections now show accurate "supports trade history" information so you know exactly what each institution will deliver, and the incremental sync window is wider so no transactions get missed between runs.

The theme this week: tell you what's going on, and make the common paths faster.

See when your bank is down

If an institution is having an outage, Redbark now shows a banner on your dashboard explaining what's happening and which of your connections are affected. You'll always know whether a quiet sync is down to your bank or down to you.

Set up multiple destinations in one flow

Onboarding now lets you connect Sheets, YNAB, and a webhook in the same session. One flow, all your destinations in place before you finish setup.

Faster API responses

Added caching in front of the API. Response times on repeat reads are noticeably quicker if you're hitting the API on a schedule.

Smaller improvements

Sheets tabs now automatically recreate themselves if they get deleted, and closed bank accounts are correctly labelled as closed in the UI.

Lots of UX tightening this week.

Pause or resume any sync

You can now pause a sync without deleting it. The whole setup sticks around (accounts, mappings, destination) until you resume. Connections that need reauthorising show an indicator so you know when action is needed, and swapping the destination on an existing sync is now a single-click flow.

One Google Sheets tab per account

If you sync more than one account to Sheets, Redbark now creates a separate tab per account automatically. Each account gets its own clean tab with its own transaction history.

A new categories endpoint

API users get a new GET /v1/categories endpoint, plus a full category reference in the docs. Transaction dates across the product now render in your timezone, so the day you see matches the day the transaction actually happened.

Smaller improvements

A small animation when a new sync card appears in the dashboard, and Airtable is no longer offered as a destination going forward.

Biggest week yet.

Redbark now has a public REST API

There's a proper /v1 API with full OpenAPI docs, API key auth, and cursor-paginated transactions. If you want to pull your banking data into something Redbark doesn't sync to natively, or just script against it, this is how. Docs live at the new API reference tab.

Map your bank accounts and categories to YNAB

You can now map each bank account to a specific YNAB account, and map your transaction categories across too. Much more precise than the automatic matching that was there before.

A new add-sync wizard

Setting up a sync is now a multi-step wizard that walks you through picking a destination, connecting the bank, and choosing which accounts go where. A lot friendlier than the old single-form approach.

Smaller improvements

A batch of reliability fixes across the sync pipeline, plus some small dashboard tweaks.

First week of the changelog. The headline is that Redbark now speaks webhook.

Point Redbark at any URL

You can now add a webhook as a destination, which means Redbark will POST your transactions to any URL you control on every sync. The payload follows Stripe's conventions (event wrapper, typed data field) and every request is HMAC-signed so you can verify it came from us. Useful if you're building your own automation on top of your bank data.

A nudge if you forget to finish setup

Connecting a bank and then never picking a destination was easy to do accidentally. There's now a gentle email reminder if you haven't finished setting up, so your data doesn't sit idle.

Smaller improvements

A handful of small fixes this week to keep syncs running smoothly.

Hello, here's what Redbark does

I've been building Redbark for months without a proper changelog, so I'm backdating one. From next Sunday I'll post a short summary every week covering what's new. This first entry is just the lay of the land.

Sync your Australian bank data wherever you want

Redbark connects to your AU bank accounts through Fiskil (Open Banking / CDR) and streams the transactions out to the tool you actually use. Today that's Google Sheets, YNAB, Notion, and Airtable. You pick a schedule, Redbark runs the sync in the background, and your data shows up where you need it.

Brokerage and NZ banking, still in development

There's an early brokerage path through SnapTrade, and NZ banking through Akahu is on the way. I'll be putting more weight behind them over the coming weeks.

The rest of the stack

A dashboard for setup and monitoring, magic-link auth, email notifications for the important stuff, and a schedule you can tweak per sync. No public API yet, no webhooks. That comes next.