A read-only API key
You create a key on the platform, allow it to look and nothing else, and paste it into Worthly. From then on the numbers arrive by themselves.
Best if you use several platforms and do not want to retype anything.
How it works
Connect a platform with a read-only key, or type your holdings in by hand. Either way, Worthly adds everything up for you and keeps the history.
Step one
You create a key on the platform, allow it to look and nothing else, and paste it into Worthly. From then on the numbers arrive by themselves.
Best if you use several platforms and do not want to retype anything.
You add what you own: an asset, a quantity, where it sits. Nothing is shared with any platform, because there is nothing to share.
Best if you would rather not hand over a key at all, or your platform has no API.
You never need a key to use Worthly. Choosing manual entry is not a downgrade, and you can mix both: some platforms by key, the rest by hand.
API keys
An API key is a pair of strings a platform generates for you. Whoever holds it can do whatever the platform allowed when you made it. That is why the permissions you tick matter more than anything else here.
Worthly asks for read-only keys and its code only ever reads: it contains no call that places an order, withdraws or transfers. But the permission itself is set and enforced by the platform, not by us, which is another reason to tick only the read box.
You can revoke a key at any time by deleting it on the platform. It stops working immediately, whatever Worthly does or does not know about it. You can also remove the connection inside Worthly.
The nightly sync
Once a day, around midnight UTC, Worthly goes through every connected platform and does the following, in order:
If one platform is slow or fails, the others still sync. Your manual holdings are included every night as well. A Refresh now button is there for the days you cannot wait. When you connect a platform for the first time, Worthly also reconstructs the history from before that day as far as the platform allows.
What it works out
Every account, in the currency you choose. Accounts can be held in EUR, USD or GBP, and are converted with live exchange rates.
A daily record of the total, so you can see where you were a month or a year ago, not only today.
How the total splits across assets and platforms, including the small leftovers you forgot about.
Dividends your holdings have paid, in one place.
What actually syncs
Built is not the same as proven. This is where each platform stands, based on what the author has run against real accounts and what the code does.
| Platform | What it reads | Status |
|---|---|---|
| Binance | Spot balances, trades, deposits and withdrawals, going back in time. Earn yield (APY) is built but has not been run against a live account yet. | Proven on a live account |
| Kraken | Spot balances and history. Kraken Futures balances are read too. Futures history is not imported. Kraken Earn is built but has not been run against a live account yet. | Proven on a live account (spot) |
| Trading 212 | Positions and history, read from its own API. | Proven on a live account |
| Bybit | Balances and spot history. Connecting and reading balances works. The history import has only run against an empty account, so it has never been seen carrying real trades. | Partly proven |
| About 100 other exchanges | Your key is checked with a single balance request, then the same import code used for the platforms above runs against it. They connect through the open-source CCXT library. Whether one of them returns history depends on that exchange, and none of them has been tried one by one. Treat them as likely, not promised. | Not proven |
| Manual entry | Any asset on any platform, typed in by you, including ones nothing can connect to. | Always available |
Platforms are checked by hand against real accounts, one at a time, which is slow. The list above will grow only when a platform has actually been seen working.