Skip to content

Missing Activity type (SPEND: PREPAID) #22

@Deigue

Description

@Deigue

Opening an item for another undetected type I discovered.
Don't have much of a preference on my end, since I am not using the cash account transactions much, figured I will leave it to you to format as desired to best match the other transaction descriptions and your own usage of the API.

[2025-10-29 <redacted>] [<redacted>-identity-<redacted>] SPEND: PREPAID -14.04 CAD
    Unknown activity:

 {'accountId': 'ca-cash-msb-<redacted>', 'aftOriginatorName': None, 'aftTransactionCategory': None, 'aftTransactionType': None, 'amount': '14.04', 'amountSign': 'negative', 'assetQuantity': None, 'assetSymbol': None, 'canonicalId': '<redacted>-identity-<redacted>', 'currency': 'CAD', 'eTransferEmail': None, 'eTransferName': None, 'externalCanonicalId': '<redacted>', 'identityId': 'identity-<redacted>', 'institutionName': None, 'occurredAt': '<redacted>', 'p2pHandle': None, 'p2pMessage': None, 'spendMerchant': 'SomeCompany', 'securityId': None, 'billPayCompanyName': None, 'billPayPayeeNickname': None, 'redactedExternalAccountNumber': None, 'opposingAccountId': None, 'status': 'settled', 'subType': 'PREPAID', 'type': 'SPEND', 'strikePrice': None, 'contractType': None, 'expiryDate': None, 'chequeNumber': None, 'provisionalCreditAmount': None, 'primaryBlocker': None, 'interestRate': None, 'frequency': None, 'counterAssetSymbol': None, 'rewardProgram': None, 'counterPartyCurrency': None, 'counterPartyCurrencyAmount': None, 'counterPartyName': None, 'fxRate': None, 'fees': None, 'reference': None, '__typename': 'ActivityFeedItem', 'description': 'SPEND: PREPAID'}

Probably interesting fields are: type, subType, status, amount, currency and spendMerchant


On somewhat related-note, I did create some generated class structures to give 'shape' to the API responses.
example: https://github.com/Deigue/folio-updater/blob/master/src/models/wealthsimple/activity_feed_item.py

But I wasn't quite sure if it would be right to put in the API library itself. This seems like territory that could easily break or cause problems.
Planning to see what extent I can create, and use them like ORM models, offering autocompletion for complex dicts/jsons

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions