For Agents
Programmatically get accounts, get transactions. Covers 3 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Swedbank Open Banking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswedbank.no%2Fswedbank-no" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswedbank.no%2Fswedbank-no" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Swedbank Open Banking API.
Get accounts
Initiate payment
Integrate Swedbank Open Banking API into automated workflows
Query and filter Swedbank Open Banking API records by parameters
GET STARTED
Use for: I need to accounts, I want to transactions, Search for initiate payment, List all records from Swedbank Open Banking API
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
Swedbank PSD2 open banking API for account information and payment initiation. The API exposes 3 endpoints secured with apiKey authentication.
Monitor Swedbank Open Banking API operational status and events
Patterns agents use Swedbank Open Banking API for, with concrete tasks.
★ Finance and Accounting Operations
Use the Swedbank Open Banking API to perform finance operations programmatically. The API provides 3 endpoints covering core functionality including get accounts, get transactions, initiate payment.
Call GET /accounts to get accounts
Automated Accounts Management
Automate accounts operations by combining multiple Swedbank Open Banking API endpoints. Agents can get transactions and then initiate payment in a single workflow.
Call GET /accounts/{accountId}/transactions to get transactions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Swedbank Open Banking API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get accounts', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — swedbank psd2 open banking api for account information and payment initiation.
METHOD
PATH
DESCRIPTION
/accounts
Get accounts
/accounts/{accountId}/transactions
Get transactions
/payments
Initiate payment
/accounts
Get accounts
/accounts/{accountId}/transactions
Get transactions
/payments
Initiate payment
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Swedbank Open Banking API by hand means passing its API key in the Authorization header on every call against api.swedbank.no and threading account and payment requests yourself. Through Jentic you install once, import the Swedbank Open Banking API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Swedbank Open Banking API puts the account id in the URL path (/accounts/{accountId}/transactions), so a rule can pin your agent to one account's transactions: it can read that data and nothing else. You choose the operations it may call, so writes like initiating a payment are not included unless you add them.
Credential isolation
Your Swedbank Open Banking API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list accounts' or 'get account transactions', and Jentic returns the matching Swedbank Open Banking API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Swedbank Open Banking API through Jentic.
What authentication does the Swedbank Open Banking API use?
The Swedbank Open Banking API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get accounts with the Swedbank Open Banking API?
Yes. Use the GET /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Swedbank Open Banking API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get accounts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get accounts'. Jentic returns the matching Swedbank Open Banking API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Swedbank Open Banking API have?
The Swedbank Open Banking API exposes 3 endpoints covering accounts, payments, transactions operations.