How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bud Financial Transaction Search API

Allows customers to search & ask questions about their financial transactions.

Bud Financial Transaction Search 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 Transaction Search. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 4 operations across 4 paths, and defines 33 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.

4 operations 4 paths 33 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.10.10
Base URL
https://api-sandbox.thisisbud.com
Authentication
HTTP Basic, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Bud Financial Transaction Search 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 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Transaction Search 4

Allows customers to search & ask questions about their financial transactions.

GET
/search/beta/transactions
Search customer transactions.
search_beta_transactions_get 19 params → 200400
GET
/search/beta/transactions/{search_id}
Get transaction search by ID.
search_beta_transactions_search_get 8 params → 200404
GET
/search/beta/transactions/{search_id}/insight
Get transaction search insight.
search_beta_transactions_insight_get 5 params → 200404
GET
/search/beta/transactions/{search_id}/insight/transactions
Get transactions used by the search insight.
search_beta_transactions_insight_transactions_get 8 params → 200404

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Transaction (19 properties), TransactionSearchQuery (12 properties), Enrichments (7 properties), Merchant (7 properties). Each schema is shown below with its type and property counts.

Token
object
The token item.
2 properties 2 required
TransactionIdSearchResult
object
2 properties 2 required
TransactionsContentType
string
Defines the transactions' format for the response. | MIME type | Description | |:-----------------------------------:|:----------------------------------------…
Merchant
object
Merchant enrichment associated with a Transaction, as generated using a combination of Bud's artificial intelligence models and database of known merchants.
7 properties
SearchInsightTransactionsResponseBodyTransactionId
object
3 properties 3 required
NextPageToken
string
The token to use to fetch the next page of results. This is only set if there are more results to fetch.
Location
object
Location enrichment associated with a Transaction
3 properties
TransactionSearchResultMatches
object
2 properties 2 required
TransactionSearchQuery
object
12 properties 2 required
Results
integer
The number of results included in this page.
BudMonetaryValue
string
The value of the monetary amount. The value is formatted with the number of decimal places for the respective currency. Example: 10.98
InsightMatchedTransactionSearch
object
A search term which has been detected in the insight text. This can be exposed as an interaction for the customer using the links & text positions provided.
3 properties 3 required
TransactionSearchResult
object
2 properties 2 required
Enrichments
object
Contextual enrichments associated with a Transaction
7 properties
SearchTransactionsResponseBodyTransactionId
object
3 properties 3 required
TransactionSearchExpirySeconds
integer
The number of seconds the search is stored. After this duration elapses, the search will expire and all requestes using it's ID will return Not Found errors.
ClientAttributes
object
An optional map of key-value string pairs that allows clients to attach arbitrary metadata to the transaction. This field can be used to store any relevant inf…
1 property
Transaction
object
A financial transaction
19 properties 8 required
TransactionSearchInsightMetadata
object
2 properties 2 required
Processor
object
Processor enrichment associated with a Transaction, as generated using a combination of Bud's artificial intelligence models and database of known payment proc…
6 properties
SearchTransactionsInsightResponseBody
object
3 properties 3 required
BudCurrency
string
The three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html) of the monetary amount. Example: GBP
TransactionFilter
object
3 properties 3 required
BudTransactionType
object
The code and a description of the transaction type. Providing these fields may help improve enrichment accuracy.
2 properties
Categories
object
Categories enrichment associated with a Transaction, as generated by Bud's artificial intelligence models. Currently two levels of category are supported, with…
2 properties
Regularity
object
Regularity enrichment associated with a Transaction, as generated by Bud's artificial intelligence models. Transactions that are similar and have a known frequ…
3 properties
SuggestedTransactionSearch
object
2 properties 2 required
TransactionFilterType
string
Transaction field used to match the search query to transactions. Current list of valid values: - merchantname - categoryl1 - categoryl2 - description - tag
Category
object
Category associated with a Transaction
2 properties 2 required
SearchTransactionsResponseBody
object
3 properties 3 required
SearchInsightTransactionsResponseBody
object
3 properties 3 required
TransactionSearchMetadata
object
4 properties 2 required
BudAmount
object
The monetary amount.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bud-co-transaction-search-api-openapi.yml Raw ↑

Other APIs Bud Financial publishes across the network.

Bud Financial Aggregation Buckets API
Bud Financial Correct Financial Data API
Bud Financial Create a Connection API
Bud Financial Custom Insights API
Bud Financial Customer Application Links API
Bud Financial Customer Applications API
Bud Financial Debt Collection Finder API
Bud Financial Enrichment Resources API
Bud Financial Enrichment Totals API
Bud Financial Frontend Widgets API
Bud Financial Income Finder API
Bud Financial Ingest First Party Data API
Where this information came from

This is an independent, third-party profile of Bud Financial Transaction Search 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.