Envestnet · Schema
BasicTransaction
Transaction object that contains details about one or more aggregated transactions.
FinancialWealth ManagementOpen BankingAccount Aggregation
Properties
| Name | Type | Description |
|---|---|---|
| id | integer | An unique identifier for the transaction. The combination of the id and account container are unique in the system. |
| amount | object | |
| date | string | The value provided will be either postDate or transactionDate. postDate takes higher priority than transactionDate, except for the investment container as only transactionDate is available. The availa |
| categoryId | string | The id of the category assigned to the transaction. This is the id field of the transaction category resource. The supported values are provided by the GET transactions/categories. |
| category | string | The name of the category assigned to the transaction. This is the category field of the transaction category resource. The supported values are provided by the GET transactions/categories. |
| link | object | Reference path link to fetch more information about the specific transaction. |
| categoryType | string | The categoryType of the category assigned to the transaction. This is the type field of the transaction category resource. categoryType primarily identifies if the transaction is an income, expense, o |
| baseType | string | Indicates if the transaction appears as a debit or a credit transaction in the account. |
| description | object | |
| sourceType | string | The source through which the transaction is added to the Yodlee system. |
| merchantType | string | Provides further information about a transaction, i.e., if the transaction is carried out on a biller, subscription merchant, or other. |
| basicMerchant | object | |
| basicPredictedEvent | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/BasicTransaction",
"title": "BasicTransaction",
"description": "Transaction object that contains details about one or more aggregated transactions.",
"properties": {
"id": {
"type": "integer",
"description": "An unique identifier for the transaction. The combination of the id and account container are unique in the system."
},
"amount": {
"$ref": "#/components/schemas/Money"
},
"date": {
"type": "string",
"description": "The value provided will be either postDate or transactionDate. postDate takes higher priority than transactionDate, except for the investment container as only transactionDate is available. The availability of postDate or transactionDate depends on the provider site."
},
"categoryId": {
"type": "string",
"description": "The id of the category assigned to the transaction. This is the id field of the transaction category resource. The supported values are provided by the GET transactions/categories."
},
"category": {
"type": "string",
"description": "The name of the category assigned to the transaction. This is the category field of the transaction category resource. The supported values are provided by the GET transactions/categories."
},
"link": {
"description": "Reference path link to fetch more information about the specific transaction.",
"allOf": [
{
"$ref": "#/components/schemas/BasicTransactionLink"
}
],
"readOnly": true
},
"categoryType": {
"type": "string",
"description": "The categoryType of the category assigned to the transaction. This is the type field of the transaction category resource. categoryType primarily identifies if the transaction is an income, expense, or some other type of transaction."
},
"baseType": {
"type": "string",
"description": "Indicates if the transaction appears as a debit or a credit transaction in the account."
},
"description": {
"allOf": [
{
"$ref": "#/components/schemas/descriptions"
}
]
},
"sourceType": {
"type": "string",
"description": "The source through which the transaction is added to the Yodlee system."
},
"merchantType": {
"type": "string",
"description": "Provides further information about a transaction, i.e., if the transaction is carried out on a biller, subscription merchant, or other."
},
"basicMerchant": {
"allOf": [
{
"$ref": "#/components/schemas/BasicMerchant"
}
]
},
"basicPredictedEvent": {
"allOf": [
{
"$ref": "#/components/schemas/BasicPredictedEvent"
}
]
}
},
"required": [
"id",
"amount",
"date",
"categoryId",
"category",
"link",
"categoryType",
"description"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/envestnet-basictransaction"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.