Webhook deliveries now come from a small, fixed set of static IP addresses
instead of a changing range, so they can be allowlisted on a firewall or
ingress. Each delivery also carries a new x-client-id header holding your
client app id.
Connecting an account that is already linked to a user has always been rejected
with 409 Conflict. That response now carries existing_institution_id, so
you can point the user at the account they already have.
Order data for Binance — both live and historical — is now available on demand, so open orders can be read rather than inferred from filled trades.
Exchanges name the same activity differently — one calls it a trade, another a
swap, another a conversion — which makes tax and accounting work painful. A new
transaction_subtype field normalises those names across connectors.
A SyncError webhook is now posted to your endpoint whenever an account
fails to sync, so a broken connection surfaces without you polling for it.
Transactions now carry a transaction_hash field — the on-chain identifier
for the movement, which can be looked up in a block explorer.
Wallet objects now carry the name of the blockchain the wallet belongs to, so a multi-chain connection no longer requires inferring the chain from the address format.
Connected Binance accounts can now be watched in real time: a websocket listens for activity and posts a webhook with the new transaction data as it happens, instead of waiting for a scheduled or manual sync.
Transactions from Binance, Coinbase and Coinbase Pro now carry additional metadata: the external address and the email associated with the movement, where the exchange reports them.
Two new error types are returned during synchronisation:
UnknownConnectorError and UnhandledConnectorError.