Skip to main content

Balance history in the API

Written by Ari Schlacht

Balance history lets your app or agent ask what any account was worth at the end of a given day, not just right now. It's the piece reconciliation automation was missing, because instead of squaring today's number against last month's books, an agent can pull the balance as of the exact day the money moved.

This is a developer feature, available through the Platform API. If you're building an integration or connecting an agent that needs to reconcile, report, or track balances over time, this is where those daily figures come from.

What you get

Sequence now keeps an end-of-day balance for every account, every day, and makes it readable through the API. You can ask for any account's balance as of any past date, with daily history building up toward a full year of coverage, and period-end figures kept well beyond that.

Because history starts building from the day this went live, the daily window fills in over time rather than reaching a full year back on day one.

How accurate is it?

It depends on the account type, and the API tells you which one you're reading:

  • For your Sequence pods and accounts, the daily figure is a true end-of-day balance.

  • For connected external accounts, it's the last balance our data providers reported that day. Each figure carries the time it was last refreshed, and it's flagged when a reconnection issue has left it stale, so your agent can tell fresh data from old.

Is it safe?

Yes. Balance history is read-only, so nothing about it can move money. An agent or key can only read the balances your account already lets it see, scoped the same way as the rest of the API, through a secure sign-in that never exposes your login details.

How it's set up

There's nothing to switch on. Once you're calling the Platform API with a scoped API key, or you've connected an agent over MCP, the daily balances are there to read, and the history keeps accruing automatically in the background from here on.

To see the endpoint, the request format, and worked examples, head to the developer docs.

Did this answer your question?