A read-only API for real bank data.

Yes. Connect gives you programmatic access to your own accounts, for your own use: your dashboards, your spreadsheets, your budgeting tools. It cannot be used to provide bank data access to anyone else. Every key and token is scoped to your own accounts, and offering the data or the access to third parties is not permitted under the terms. If someone else wants Endute data, they need their own Endute account.

You authenticate directly with your bank through regulated open banking and consent to read-only access. Connect then serves those accounts, balances and transactions. It is strictly read-only: it cannot move money or change anything at the bank. It never sees your bank password, only the access the bank issues.

You are billed per connected account, bank or investment, at the same rate. £3.99 a month covers your first 5; each extra account is £0.50 a month. Deactivating an account stops it billing immediately and it drops off your next invoice, while its history stays available on the API. Sandbox accounts are always free. If a bank revokes a connection (suspended), those accounts keep billing until you deactivate them or the connection moves to an error state; accounts on error or superseded connections do not bill.

Your keys are never deleted when a payment fails, and the data already synced to your account is kept. There is a grace period, with warning emails before anything changes. During a lapse the API returns a clear 403 with a machine-readable code, and once you renew, the same keys resume working. If a lapse runs on long enough, the underlying bank connections are eventually revoked at the provider (we email you first), and those need reconnecting after you renew.

Yes. Provision a deterministic sandbox bank from the portal and call every endpoint with realistic data, with the exact same shapes as production. Sandbox accounts never bill, so you can develop and test end to end for free.

Each API key is limited to 120 requests per minute, and your developer account to 50,000 requests per day across all of its keys. When you hit a limit you get a 429 with a Retry-After header telling you how long to wait.

Connect syncs bank data on a schedule rather than on every request, typically hourly, with some banks refreshing a few times a day. Balances are cached and every balance response tells you when it was last fetched. See the data freshness page in the docs for the full detail, including duplicate handling and history depth.

Keys are shown once at creation and only their SHA-256 hash is stored, so a database leak exposes no usable secret. Every key starts with the edk_ prefix and matches a fixed pattern (edk_[A-Za-z0-9_-]{8}_[A-Za-z0-9_-]{43}) so you can scan your own code and logs for accidental leaks. The API is read-only, data is served straight from our aggregation engine, and every request is scoped to the key owner’s own accounts.