Different endpoints that allow to to manage an existing customer connection. This includes the ability to: (i) Refresh the data associated with a given connection, pulling in the latest account information into the Bud platform; (ii) Renew an existing consent by-passing the need to go through Strong Customer Authentication (SCA) with their bank; (iii) Revoke a consent, removing the ability for Bud to fetch any further data associated with that consent.
Bud Financial Manage a Connection API is one of 32 APIs that Bud Financial publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Manage a Connection. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.
This API exposes
8 operations
across 8 paths,
and defines 40 schemas.
It is described by OpenAPI 3.2.0, at version 2.10.10.
Requests are made against a single base URL, https://api-sandbox.thisisbud.com.
8 operations8 paths40 schemas4 GET4 POST
Metadata
The identity and technical contract details declared by the specification.
Bud Financial Manage a Connection API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (Basic).
It supports OAuth 2.0 (OAuth2) using the clientCredentials flow.
OAuth2 — Authentication flow: 1. Perform OAuth2 Client Credentials authentication using API Credentials (clientid,clientsecret) to obtain an accesstoken against /v1/oau…
Paths & Operations 8
Across 8 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.
Manage a Connection 8
Different endpoints that allow to to manage an existing customer connection. This includes the ability to: (i) Refresh the data associated with a given connection, pulling in the…
The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are GetOBConsentsResponseDataItem (17 properties), ProviderOBV2WebhookBody (13 properties), RefreshSubtaskWebhookTask (11 properties), OBV2WebhookBody (9 properties). Each schema is shown below with its type and property counts.
SubTaskV2View
object
A task view.
6 properties
TaskId
string
Bud Task identifier returned from an async task for the requested action
Indicator as to whether the account needs to be connected again, through SCA authentication.
GetOBConsentsResponse
object
3 properties2 required
RefreshSubtaskWebhookTask
object
The payload detailing an individual refresh for a single provider
11 properties6 required
OBConsentWebhookBody
object
The payload sent to the client defined webhook (via the console) when an event occurs to a Open Banking Consent.
1 property1 required
OBV2WebhookBody
object
The payload sent to the client defined webhook (via the console) when an Open Banking refresh V2 task completes.
9 properties6 required
ConsentReconfirmation
object
Result of performing a reconfirmation of consent task
2 properties2 required
TaskStatusCaps
string
The general status of a task
TaskCreatedView
object
Standard successful task created response.
2 properties2 required
ReconfirmConsentResponse
object
Expected response payload structure
2 properties2 required
ProviderOBV2WebhookBody
object
The payload sent to the client defined webhook (via the console) when an Open Banking refresh V2 task completes.
13 properties8 required
OpenBankingRefreshV2Response
object
Expected response structure
3 properties3 required
BadRequestResponse
object
Expected response structure
4 properties4 required
ConnectResultCodes
string
The result of the operation. Either success or various error codes.
OpenBankingRefreshRequest
object
Expected request payload structure
3 properties1 required
TaskV2View
object
A task view.
5 properties
OpenBankingRefreshRequestV2
object
Expected request payload structure
4 properties
TaskView
object
A task view.
7 properties
RawOBConsents
objectnull
The raw consent as returned by the provider
6 properties
OBRefreshWebhookBody
object
The payload sent to the client defined webhook (via the console) when an Open Banking (connect or refresh) task completes.
1 property1 required
OBSyncWebhookBody
object
The payload sent to the client defined webhook (via the console) when an Open Banking Synchronisation (connect or refresh) task completes.
2 properties1 required
AsyncTaskMetadata
object
Metadata associated with an asynchronous task
3 properties
OpenBankingRefreshResponse
object
Expected response structure
3 properties3 required
RevokeTaskCreatedResponse
object
Expected response structure
3 properties3 required
TaskType
string
The type of task that completed
TaskV2CreatedView
object
Standard successful task created response.
2 properties2 required
ResultsMetadata
object
Metadata associated with the response schema
1 property
GetOBConsentsResponseDataItem
object
Schema to define a given Open Banking consent
17 properties12 required
RevokeAccountAccessIntentTastStatusResponse
object
Expected response from a get status request for a revoke account access intent call
3 properties3 required
Error
objectnull
Contains a field specific error message
Errors
object
Contains a list of error messages
TaskCreatedResponseOB
object
Expected response structure
3 properties3 required
HasNewTransactions
boolean
To describe whether new transactions have been pulled from the relevant ASPSP during the refresh. Note that if this field is set to false then there is no need…
TaskCreatedV2ResponseOB
object
Expected response structure
3 properties3 required
RevokeAccountAccessIntentRequest
object
1 property1 required
TaskCreatedMetadata
object
Created task metadata response
3 properties3 required
OBResources
string
OperationId
string
A unique identifier/reference associated with a given endpoint/operation
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Bud Financial Manage a Connection API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
