Actions13
- Accounts Actions
- Orders Actions
- Transactions Actions
- User Preference Actions
Overview
This node interacts with the Schwab Trader API to retrieve transaction data for a specified account. Specifically, the "Get Transactions By Path Param" operation fetches transactions filtered by account number and other optional parameters such as date range, symbol, and transaction types.
Common scenarios where this node is beneficial include:
- Financial reporting workflows that require fetching detailed transaction histories.
- Portfolio management automation where transaction data needs to be analyzed or synchronized.
- Auditing or compliance processes that need filtered transaction records within specific time frames.
For example, you can use this node to get all trade transactions for a particular account between two dates, optionally filtering by a specific stock symbol.
Properties
| Name | Meaning |
|---|---|
| Account Number | The encrypted ID of the account for which transactions are retrieved. This is a required string input. |
| Start Date | The start of the date range filter; no transactions before this ISO-8601 formatted timestamp will be returned. Required when specifying an end date. Example: 2024-03-28T21:10:42.000Z. |
| End Date | The end of the date range filter; no transactions after this ISO-8601 formatted timestamp will be returned. Required when specifying a start date. Example: 2024-05-10T21:10:42.000Z. |
| Symbol | Optional filter to return only transactions related to a specific symbol (e.g., stock ticker). If the symbol contains special characters, it should be URL encoded. |
| Types | Required filter specifying the type of transactions to return. Options include: TRADE, RECEIVE AND DELIVER, DIVIDEND OR INTEREST, ACH RECEIPT, ACH DISBURSEMENT, CASH RECEIPT, CASH DISBURSEMENT, ELECTRONIC FUND, WIRE OUT, WIRE IN, JOURNAL, MEMORANDUM, MARGIN CALL, MONEY MARKET, SMA ADJUSTMENT. |
| Additional Headers | Optional custom HTTP headers to send with the request. Useful for adding extra metadata or identifiers. Authorization headers are handled automatically and should not be added here. |
Output
The node outputs JSON objects representing the transactions retrieved from the Schwab API. Each output item corresponds to one transaction record with fields as returned by the API.
- The output JSON structure directly reflects the API response for transactions.
- If multiple transactions are returned, each is emitted as a separate item.
- No binary data output is produced by this node.
Dependencies
- Requires an OAuth2 API credential configured for authenticating with the Schwab Trader API.
- The node sends requests to the base URL:
https://api.schwabapi.com/trader/v1. - Proper API access permissions and valid tokens are necessary to successfully retrieve transaction data.
Troubleshooting
- Missing or invalid credentials: Ensure the OAuth2 credential is correctly set up and authorized.
- Invalid date formats: The
startDateandendDatemust be in valid ISO-8601 format (yyyy-MM-dd'T'HH:mm:ss.SSSZ). Incorrect formats will cause request failures. - Required parameters missing: Both
accountNumber,startDate,endDate, andtypesare mandatory. Omitting any will result in errors. - API rate limits or network issues: Network errors or rate limiting by the Schwab API may cause request failures. Check connectivity and API usage quotas.
- Error messages: The node surfaces error messages including HTTP status codes and API response data. Review these details to diagnose issues.
- Special characters in symbol: If the symbol contains special characters, ensure it is URL encoded to avoid request errors.
Links and References
- Schwab Trader API Documentation (official API docs for reference)
- ISO 8601 Date Format (for correct date formatting)