Transactions

A Transaction in Quiltt represents financial activity associated with an Account. Transactions can include basic banking activities like deposits and withdrawals, as well as investment activities with associated securities and fees.

Metadata

Like many other resources, transactions support persisting arbitrary information via a `metadata` object. This can be used to store nicknames, custom timestamps, status indicators and other data that may be useful to retrieve later. See the API Reference or the Custom Metadata guide for more information.

Link to this section#Schemas & Types

Profile GraphQL API Reference

To access the full documentation and typings, explore the schema in the GraphQL API Reference. or use the GraphQL Explorer in the Quiltt Dashboard

Link to this section#Queries

Transaction queries allow you to fetch data about specific transactions or lists of transactions associated with the Profile or an Account.

Link to this section#The `transaction` Query

Looks up a Transaction by its ID:

Link to this section#Response

Link to this section#The `transactions` Query

Lists and filters the Transactions associated with the Profile:

Link to this section#Response

Link to this section#Filtering Transactions

The transactions query supports various filtering options:

Link to this section#Filter by Amount

Link to this section#Filter by Date Range

Link to this section#Filter by Account Type

Link to this section#Mutations

Transaction mutations allow you to update individual Transactions.

Link to this section#The `transactionUpdate` Mutation

Updates a Transaction with new metadata. This is useful for storing additional information about the Transaction:

Link to this section#Response

Link to this section#Remote Data

Transactions include remote data from various providers and enrichment services. You can access this data through the remoteData field:

See the Remote Data guide for more information about accessing and working with provider-specific transaction data.