get_transaction — Retrieve a single transaction

The get_transaction tool returns a single transaction by transactionId within an organization. Use it when your agent already knows the transaction ID and needs full details. intent, organizationId, and transactionId are required, and the token must carry the transactions.read scope.

Scope

Required OAuth scope: transactions.read

Input

string

required

The organization that owns the transaction. Must be one of the organizations the token can access.

string

required

The unique transaction identifier to retrieve.

string

required

What the user asked for and why this call serves it, in 1 to 500 characters. Required on every tool call. See Common tool arguments.

Output

Transaction

required

The requested transaction object.

Show Transaction

string

required

Always "transaction".

string

required

Unique transaction identifier.

string

required

Organization the transaction belongs to.

string

required

Account the transaction belongs to.

string | null

required

Card associated with the transaction, if any.

Money

required

Unsigned amount as a Money object. Use direction for the sign.

string

required

Always "USD".

string

required

Sign carrier for the amount. Values: debit, credit.

string

required

Transaction lifecycle status. Values: created, processing, settled, returned, canceled, pending, unknown.

string

required

Payment rail. Values: ach, wire, card, check, transfer, fee, interest, other.

string

required

Human-readable description.

string

required

Name of the counterparty.

string

required

Category of the counterparty.

string

required

Timestamp when the transaction occurred, in RFC 3339 format.

Example

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "get_transaction",
    "arguments": {
      "intent": "User asked for the details of a specific payment they referenced.",
      "organizationId": "org_1",
      "transactionId": "txn_1"
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "structuredContent": {
      "data": {
        "object": "transaction",
        "id": "txn_1",
        "organizationId": "org_1",
        "accountId": "acc_1",
        "cardId": null,
        "amount": { "cents": 12500, "display": "125.00", "currency": "USD" },
        "currency": "USD",
        "direction": "debit",
        "status": "settled",
        "type": "card",
        "description": "Coffee",
        "counterpartyName": "Blue Bottle",
        "counterpartyCategory": "restaurants",
        "occurredAt": "2026-07-01T14:03:00.000Z"
      }
    }
  }
}

Error message

If the transaction does not exist or is not accessible with the provided token, the tool returns an MCP error:

Transaction not found or not accessible.

list_transactions

Search and list transactions with filters and pagination.

Errors

Learn how MCP tool errors and HTTP auth failures are surfaced.

Organizations

Transactions

Accounts

Cards

Statements

Contacts

Catalog items

Invoices

get_transaction — Retrieve a single transaction

Scope

Input

Output

Example

Error message

list_transactions

Errors

​Scope

​Input

​Output

​Example

​Error message

list_transactions

Errors

Scope

Input

Output

Example

Error message