canonical: https://jentic.com/apis/wealthapi.eu/wealthapi-eu

# wealthAPI

The wealthAPI API is a RESTful interface for accessing the wealthAPI system programmatically. It provides endpoints for account, investment and transaction management and analytics (PURE core API) as well as access to brokerage connections (brokerage API). The API uses JWT bearer token authentication and supports mandator-based multi-tenancy. The API exposes 11 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically login and obtain auth token, refresh auth token. Covers 11 operations with apiKey, bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Login and obtain auth token
- Refresh auth token
- List bank accounts
- Get account by ID
- Delete an account

## Use cases

### Payments Operations

Use the wealthAPI to perform payments operations programmatically. The API provides 11 endpoints covering core functionality including login and obtain auth token, refresh auth token, list bank accounts.

Example prompt: Call POST /login to login and obtain auth token

### Automated Authentication Management

Automate authentication operations by combining multiple wealthAPI endpoints. Agents can refresh auth token and then list bank accounts in a single workflow.

Example prompt: Call POST /refreshToken to refresh auth token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call wealthAPI 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, bearer tokens manually.

Example prompt: Search Jentic for 'login and obtain auth token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login` | Login and obtain auth token |
| POST | `/refreshToken` | Refresh auth token |
| GET | `/accounts` | List bank accounts |
| GET | `/accounts/{id}` | Get account by ID |
| DELETE | `/accounts/{id}` | Delete an account |
| GET | `/transactions` | List transactions |
| GET | `/funds` | List funds |
| POST | `/users` | Create a new user |

## Key resources

- **Authentication** — Login and token management
- **Accounts** — Bank account management
- **Transactions** — Transaction data
- **Investments** — Investment portfolio management
- **Funds** — Fund data

## 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:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 34 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 58 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/wealthapi.eu/wealthapi-eu/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 wealthAPI by hand means learning its bearer token alongside the mandator client id and secret headers, pointing at the sandbox host, and handling responses yourself. Through Jentic you install once, import wealthAPI from the API Directory, store those credentials once, and your agent calls it.
- **Permission scoping:** wealthAPI puts the account id in the URL path (`/accounts/{id}`), so a rule can pin your agent to one account and nothing else. You choose the operations it may call, so destructive ones like deleting an account are not included unless you add them.
- **Credential handling:** Your wealthAPI token and mandator client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list accounts' or 'get transactions', and Jentic returns the matching wealthAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the wealthAPI use?

The wealthAPI uses apiKey, bearer authentication. 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 login and obtain auth token with the wealthAPI?

Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the wealthAPI?

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 login and obtain auth token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login and obtain auth token'. Jentic returns the matching wealthAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the wealthAPI have?

The wealthAPI exposes 11 endpoints covering authentication, accounts, transactions operations.

### Can I limit what my agent is allowed to do with the wealthAPI?

Yes. Because you run Jentic One yourself, your own rules decide which wealthAPI operations and credentials the agent may use, so you can grant read calls like GET /accounts and GET /transactions while withholding destructive ones such as DELETE `/accounts/{id}` unless you explicitly add them. Since wealthAPI puts the account id in the URL path (`/accounts/{id}`), a rule can pin the agent to a single account and block every other one. The stored token and mandator client credentials are injected only when an allowed operation runs, so the agent can never reach an endpoint you have not approved.