canonical: https://jentic.com/apis/swedbank.no/swedbank-no

# Swedbank No Swedbank Open Banking API

Swedbank PSD2 open banking API for account information and payment initiation. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get accounts, get transactions. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Get accounts
- Initiate payment
- Integrate Swedbank Open Banking API into automated workflows
- Query and filter Swedbank Open Banking API records by parameters
- Monitor Swedbank Open Banking API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get accounts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts` | Get accounts |
| GET | `/accounts/{accountId}/transactions` | Get transactions |
| POST | `/payments` | Initiate payment |

## Key resources

- **Accounts** — Operations related to Accounts
- **Payments** — Operations related to Payments
- **Transactions** — Operations related to Transactions

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/swedbank.no/swedbank-no/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Swedbank Open Banking API?

Yes. Because you run Jentic One yourself, your own rules decide which Swedbank Open Banking API operations and credentials the agent may use. You pick the operations it can call, so you can grant read-only access to GET /accounts and GET `/accounts/{accountId}/transactions` while excluding the payment write POST /payments. Since the account id sits in the URL path, a rule can also pin the agent to a single account's transactions so it reads that data and nothing else.