Bud Financial Platform API

Name: Bud Financial Platform API API
Brand: Bud Financial Platform API
Availability: InStock

✓ Official Vendor SpecFinanceBankingbearer8 EndpointsREST

For Agents

Provision customers, retrieve their aggregated Open Banking accounts and transactions, and manage bank connections via Bud's financial data platform.

Quickstart

Get started with Bud Financial Platform 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 a customer's bank transactions"

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

Capabilities

What an agent can do with Bud Financial Platform API API.

Mint OAuth bearer tokens for the Bud platform via /v1/oauth/token

Create and look up end customers in the Bud platform with createcustomer and getcustomer

List all customers tied to a Bud client account for back-office tooling

Retrieve a customer's aggregated bank accounts across UK and EU Open Banking providers

GET STARTED

Start building with Bud Financial Platform API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Bud Financial Platform API API for, with concrete tasks.

★ Affordability and Cash-Flow Underwriting

Underwrite consumer loans, mortgages, or rent applications using real bank-account behaviour rather than self-reported income. After the customer connects their bank through Bud Connect, the lender retrieves /financial-data/v3/accounts to confirm balances and /financial-data/v3/transactions to compute monthly inflows, recurring outgoings, and discretionary spend. Bud's category labels make it easy to classify rent, salary, and gambling outflows for affordability calculators.

Call listaccounts for the customer's customer_id, then call listtransactions filtered to the last 90 days and aggregate inflows by category

Account Verification Before Direct Debit

Verify that a customer owns the bank account they are about to set up a direct debit on by retrieving /connect/v2/connections after the consumer's Bud Connect flow completes. The connection record returns the institution and the verified account holder name so the merchant can match it to the application form before submitting a SEPA or Bacs mandate. This reduces failed mandates and chargebacks.

Call listconnections on /connect/v2/connections for the customer and confirm the returned account holder name matches the application form

Personal Finance Dashboard Backend

Build a personal finance management app where each end user is created via /platform/v3/customers, links their bank through Bud Connect, and the app then renders categorised transactions retrieved via /financial-data/v3/transactions. The same listaccounts call returns balances across current, savings, and credit accounts so the dashboard can show net position. Bud handles the underlying Open Banking provider connections.

Create a customer with createcustomer, store the returned customer_id, and on each refresh call listtransactions with that customer_id for the dashboard view

AI Agent Open Banking Through Jentic

Allow an AI agent to inspect a consented user's bank data on their behalf without ever holding the Bud platform JWT. Through Jentic, the agent searches by intent, loads the listtransactions schema, and executes against /financial-data/v3/transactions with the customer_id supplied by the consented user's session. The OAuth token is minted and refreshed by Jentic at execution time so the agent never touches client credentials.

Use Jentic to search 'list a customer's bank transactions', load the listtransactions schema, and execute with the consented customer_id and a date range

Key Endpoints

8 endpoints — bud financial's platform api gives banks, lenders, and fintechs access to uk and eu open banking data through a single rest surface.

METHOD

PATH

DESCRIPTION

POST

/v1/oauth/token

Mint a bearer access token

POST

/platform/v3/customers

Create an end customer in the Bud platform

GET

/platform/v3/customers

List all customers tied to your client account

GET

/platform/v3/customers/{customer_id}

Retrieve a single customer by ID

DELETE

/platform/v3/customers/{customer_id}

Delete a customer record

GET

/financial-data/v3/accounts

List a customer's aggregated bank accounts

GET

/financial-data/v3/transactions

List a customer's bank transactions

GET

/connect/v2/connections

List a customer's authorised bank connections

POST

/v1/oauth/token

Mint a bearer access token

POST

/platform/v3/customers

Create an end customer in the Bud platform

GET

/platform/v3/customers

List all customers tied to your client account

GET

/platform/v3/customers/{customer_id}

Retrieve a single customer by ID

DELETE

/platform/v3/customers/{customer_id}

Delete a customer record

Why though Jentic?

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

Credential isolation

The Bud client_id and client_secret are stored encrypted in the Jentic vault. Jentic mints and refreshes OAuth bearer tokens via /v1/oauth/token at execution time and injects only the bearer token into the outgoing request, so the client secret never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list a customer's bank transactions') and Jentic returns the matching listtransactions operation with its parameter schema, so the agent calls /financial-data/v3/transactions without browsing Bud's docs.

Time to first call

Direct Bud integration: 5-10 days for OAuth handling, customer provisioning, Connect callbacks, and transaction enrichment. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Buckaroo Checkout JSON Gateway API

European payment gateway used to debit accounts after Bud has verified ownership

Pair Buckaroo with Bud when an agent should verify the bank account through Bud and then collect payment via Buckaroo SEPA

Complementary

Buckaroo Checkout JSON Gateway API

Same Buckaroo gateway sourced from buckaroo.nl for SEPA charging after Bud verification

Use when the merchant prefers the buckaroo.nl spec source for the downstream payment step

Complementary

Bubble Data API

Stores Bud customer IDs and underwriting decisions in a no-code Bubble app

Use when an internal Bubble-based ops tool needs to persist the result of a Bud-driven affordability check

FAQs

Specific to using Bud Financial Platform API API through Jentic.

What authentication does the Bud Financial Platform API use?

Bud uses OAuth 2.0 bearer tokens in JWT format. POST your client_id and client_secret to /v1/oauth/token to receive an access_token, then send Authorization: Bearer <token> on subsequent requests. Through Jentic the client credentials are stored encrypted in the vault and the OAuth exchange runs server-side so they never enter the agent's context.

Can I retrieve a customer's bank transactions with this API?

Yes, after the customer has authorised an Open Banking connection through Bud Connect. GET /financial-data/v3/transactions with the customer_id query parameter returns categorised transactions across all the customer's connected accounts. Combine with /financial-data/v3/accounts to retrieve balances at the same time.

What are the rate limits for the Bud Financial API?

Bud applies per-client rate limits that vary between the sandbox and production environments. Specific values are not encoded in the spec — see the Bud client portal at docs.thisisbud.com for the limits assigned to your account. The API returns standard 429 responses when throttled and clients should back off before retrying.

How do I create a Bud customer through Jentic?

Install the SDK with pip install jentic, search for 'create a Bud customer', load the createcustomer schema, and execute it against /platform/v3/customers with the customer's name and email. Jentic mints and refreshes the OAuth token from the vault and returns the new customer_id you can store for later /financial-data/v3/* calls.

Does this API include Open Banking consent collection?

No. The Bud Financial Platform API itself does not host the consent flow — consent is collected through the Bud Connect product, which redirects the consumer to their bank to authorise data sharing. Once consent is granted the connection appears in /connect/v2/connections and accounts and transactions become accessible via the financial-data endpoints.

Is the Bud Financial API free?

Bud is a paid platform sold to banks, lenders, and regulated fintechs. Pricing is negotiated per client and depends on call volume and the Bud products enabled (Connect, Aggregation, Transaction Categorisation, etc.). Sandbox access is provided for integration; see thisisbud.com for commercial terms.