Account Transactions
Loading...
Loading...
Loading...
A Transaction in Quiltt represents financial activity associated with an Account. Account Transactions can include basic banking activities like deposits and withdrawals, as well as investment activities with associated securities and fees.
Transaction queries allow you to fetch data about specific transactions or lists of transactions associated with the Profile or an Account.
transactionLooks up a Transaction by its ID:
query {
transaction(id: "txn_11VgTOO9DR1vbAZxb6zBLdb") {
id
date
description
amount
entryType
status
account {
id
name
}
}
}
{
"data": {
"transaction": {
"id": "txn_11VgTOO9DR1vbAZxb6zBLdb",
"date": "2024-06-09",
"description": "GROCERY STORE",
"amount": 56.78,
"entryType": "DEBIT",
"status": "POSTED",
"account": {
"id": "acct_12tgD1YP33AwEvbdmSrcRY",
"name": "Checking Account"
}
}
}
}
transactionsThis query uses cursor-based pagination, based on the
Relay Connection Specification.
Connection page size is capped at 100 records per request. If you prefer
smaller pages, pass first and continue pagination with pageInfo.endCursor
until hasNextPage is false. See our
Pagination guide for examples and best practices.
Lists and filters the Transactions associated with the Profile:
query GetTransactions {
transactions(
first: 10,
sort: DATE_DESC,
filter: {
status: [POSTED],
entryType: DEBIT
}
) {
count
edges {
node {
id
date
description
amount
entryType
status
account {
name
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}
{
"data": {
"transactions": {
"count": 42,
"edges": [
{
"node": {
"id": "txn_11VgTOO9DR1vbAZxb6zBLdb",
"date": "2024-06-09",
"description": "GROCERY STORE",
"amount": 56.78,
"entryType": "DEBIT",
"status": "POSTED",
"account": {
"name": "Checking Account"
}
}
},
...
],
"pageInfo": {
"hasNextPage": true,
"endCursor": "cursor_value_here"
}
}
}
}
The transactions query supports various filtering options:
query {
transactions(filter: {
amount_gte: 100,
amount_lte: 500
}) {
count
nodes {
id
amount
description
}
}
}
query {
transactions(filter: {
date_gte: "2024-01-01",
date_lte: "2024-01-31"
}) {
count
nodes {
id
date
amount
}
}
}
query {
transactions(filter: {
kind: [DEPOSITORY, CREDIT]
}) {
count
nodes {
id
account {
name
type
}
}
}
}
Transaction mutations allow you to update individual Transactions.
transactionUpdateUpdates a Transaction with new metadata. This is useful for storing additional information about the Transaction:
mutation TransactionUpdate {
transactionUpdate(
input: {
id: "txn_11VgTOO9DR1vbAZxb6zBLdb",
metadata: {
category: "Groceries",
notes: "Weekly shopping"
}
}
) {
success
record {
id
metadata
}
}
}
{
"data": {
"transactionUpdate": {
"success": true,
"record": {
"id": "txn_11VgTOO9DR1vbAZxb6zBLdb",
"metadata": {
"category": "Groceries",
"notes": "Weekly shopping"
}
}
}
}
}
Transactions include remote data from various providers and enrichment services. You can access this data through the remoteData field:
query {
transaction(id: "txn_11VgTOO9DR1vbAZxb6zBLdb") {
id
remoteData {
ntropy {
enrichment {
response {
labels
logo
website
}
timestamp
}
}
mx {
transaction {
response {
guid
description
originalDescription
}
timestamp
}
}
}
}
}
See the Remote Data guide for more information about accessing and working with provider-specific transaction data.