Guides
Authentication & permissions
Use Account → API keys at https://app.bankmcp.app/account, or the MCP create_api_key tool. MCP requires the explicit api-keys:create OAuth permission and the banking scopes for the requested API permissions. Reauthorize the assistant once if needed. Example arguments:
{
"name": "Spending dashboard",
"permissions": ["accounts:read", "balances:read", "transactions:read"],
"resources": { "type": "all" },
"ttl_seconds": 604800
}
Omitted TTL means three UTC calendar months, clamped to month end. Custom TTL is a positive integer number of seconds, at most 2147483647. Omitted permissions and resources mean full access. The server rejects scope escalation instead of silently reducing access. The result includes the one-time secret, expiration, restrictions and API/docs URLs.
Keys have independent lifetimes: disconnecting the issuing assistant does not revoke them. Revocation, expiration, account deletion and explicit sign-out-everywhere stop access. Ordinary browser sign-out does not. Save the secret immediately; it cannot be retrieved again. A lost creation response requires inspecting your key list and explicitly creating a replacement, not blindly retrying.
Permissions and resources
Each reference operation names its required permission. Resource restrictions are additional:
{"type":"all"}allows all current and future accounts.{"type":"banks","bank_ids":["DE:N26"]}allows those connected banks, including their future accounts.{"type":"accounts","account_ids":["account-id"]}allows only those accounts. Grants retain stable internal identity through bank reconnection; discover current API account IDs again after reconnecting.
Account-only keys cannot run bank-wide refresh/import/disconnect or create connection links. Customer-wide merchant operations require all-account access and enabled enrichment. Out-of-scope resources return 404 without confirming their existence. Bank lists contain identity only, not balances. Linked wallet data from excluded accounts is not returned. API keys cannot create additional keys or sign in as a customer or administrator.
Replacement and revocation
Create a replacement key with the desired expiration, operations and accounts, update your backend environment, verify a request, then revoke the old key in Banking Account. Changing the display name does not affect access. Public API documentation does not remove the current pilot eligibility restriction.