Budgea API

Name: Budgea API API
Brand: Budgea API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingnone167 EndpointsREST

For Agents

Aggregate bank accounts, fetch normalised transactions, categorise spending, and initiate SEPA payments across European banks via the Budgea open banking platform.

Quickstart

Get started with Budgea API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list user bank transactions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Budgea API API.

Connect end users to French and European banks under PSD2 access-to-account

Fetch normalised transaction history across linked bank accounts

Categorise transactions using the Budgea category taxonomy and keyword rules

Initiate SEPA credit transfers and recurring payments through PSD2 payment initiation

GET STARTED

Start building with Budgea API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Budgea API, keeping it validated and agent-ready.

The Budgea API by Powens (formerly Budget Insight) is an open banking aggregation platform covering PSD2-regulated bank connections, account information, transaction history, payment initiation, and personal finance management features. Agents can connect end users to French and European banks, retrieve normalised transaction feeds, categorise spending, and trigger SEPA payments. The spec exposes 167 endpoints across banking connectors, accounts, transactions, categories, users, webhooks, and document-based wealth aggregation. Authentication relies on JWT tokens minted from /auth/jwt and user access tokens minted from /auth/token.

Use Cases

Patterns agents use Budgea API API for, with concrete tasks.

★ Personal Finance Management Aggregator

Build a PFM application that aggregates a user's bank accounts across multiple French and European banks, categorises every transaction, and produces a monthly spending breakdown. Budgea handles the PSD2 connection lifecycle, normalises transactions across banks, and applies a category taxonomy with keyword rules. Typical integration time for a PFM MVP is 3-4 weeks including the redirect flow.

Fetch every account and the last 90 days of transactions for user 9876, then group totals by category.

SEPA Payment Initiation

Trigger payments directly from a connected bank account under PSD2 payment initiation services. Budgea brokers the redirect to the user's bank for strong customer authentication, then returns the payment status. This is suitable for invoice settlement, recurring rent collection, and account-funded e-commerce checkout in the EU.

Initiate a 250 EUR SEPA transfer from connection 4567 to IBAN FR76xxxxxxxxxxxxxxxxx with reference 'INV-2026-001'.

Lending Underwriting Data Pull

Pull a normalised income and expenditure feed from a borrower's bank account to underwrite a loan. The Budgea connection delivers categorised transactions, recurring income detection, and account balance trends. Lenders avoid building per-bank scrapers and rely on the Budgea connector catalogue, which covers most retail banks in France and major European markets.

Retrieve 12 months of transactions from user 1234's primary current account and flag every recurring salary deposit.

AI Agent Spending Coach

An AI agent acts as a spending coach, answering questions like 'how much did I spend on dining this month?' by querying Budgea through Jentic. The agent does not handle JWT minting itself — Jentic stores both the manage token and per-user tokens in the vault and injects the right credential per call.

Search Jentic for 'list user transactions Budgea', load the schema, and return all dining-category transactions for the current month.

Key Endpoints

167 endpoints — the budgea api by powens (formerly budget insight) is an open banking aggregation platform covering psd2-regulated bank connections, account information, transaction history, payment initiation, and personal finance management features.

METHOD

PATH

DESCRIPTION

POST

/admin/jwt

Generate a manage JWT token

POST

/auth/jwt

Generate a user JWT token

POST

/auth/token

GET

/banks

List supported bank connectors

GET

/categories

List the category taxonomy

POST

/admin/jwt

Generate a manage JWT token

POST

/auth/jwt

Generate a user JWT token

POST

/auth/token

GET

/banks

List supported bank connectors

GET

/categories

List the category taxonomy

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Budgea manage tokens and per-user JWTs are stored encrypted in the Jentic vault (MAXsystem). Agents call Budgea operations via Jentic and the right token is injected based on whether the call is admin-scoped or user-scoped — raw JWTs never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list user bank transactions') and Jentic returns the matching Budgea operation with its parameters, so agents do not need to navigate the 167-endpoint reference to find the right user transactions endpoint.

Time to first call

Direct Budgea integration: 3-4 weeks for the OAuth-style redirect flow, dual-token model, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Plaid API

Plaid is the dominant open banking aggregator in the US and Canada, where Budgea has limited coverage.

Choose Plaid for North American bank coverage; choose Budgea for France and major European markets.

Alternative

TrueLayer API

TrueLayer offers PSD2 aggregation and payments with strong UK and EU coverage.

Choose TrueLayer when UK coverage is the priority; choose Budgea when French coverage is the priority.

Complementary

GoCardless API

GoCardless collects recurring direct debits that can be reconciled against Budgea-aggregated bank accounts.

Use GoCardless to collect a Direct Debit and Budgea to confirm the funds arrived in the merchant's account.

FAQs

Specific to using Budgea API API through Jentic.

What authentication does the Budgea API use?

Budgea uses JWT tokens. POST to /admin/jwt for a manage token (tied to your client credentials) and POST to /auth/jwt or /auth/token to mint a per-user token after a user has connected. Through Jentic, both tokens are stored encrypted in the Jentic vault and injected at execution time so the agent never handles raw secrets.

Can I initiate SEPA payments with the Budgea API?

Yes. Budgea offers PSD2 payment initiation services and the spec includes payment-related endpoints under the /users and /banks resources. The user's bank handles strong customer authentication via redirect; Budgea returns the payment status to your application.

What are the rate limits for the Budgea API?

Rate limits are tier-dependent and not declared in the OpenAPI spec. Powens documents quotas in the partner agreement; expect HTTP 429 with a Retry-After header when limits are hit. Manage-token-scoped calls are rate-limited per client; per-user calls are limited per user-token.

How do I list a user's transactions through Jentic?

Search Jentic for 'list user transactions Budgea', load the matching operation, and execute with the user_id. With the SDK: pip install jentic, then SearchRequest, LoadRequest, ExecutionRequest in an async flow — Jentic injects the right user JWT for the call.

Which banks does Budgea cover?

GET /banks returns the live catalogue of supported connectors. Coverage is strongest in France and major European markets. Each connector entry exposes fields such as the required login parameters and the connector's source feed (PSD2 API or web aggregation fallback).

Does Budgea support webhooks for transaction updates?

Yes — Budgea exposes webhook subscriptions so your application can be notified when transactions change or a connection moves into an error state. Configure webhook URLs in the Powens admin console and consume them via your own HTTPS endpoint.