Nessie v2 transactions: KeyError: 'type' and tx['merchant']['name'] crash: the field is `kind` and there is no merchant object; parse with a pydantic discriminated union
Symptom: tools that summarised Nessie v2 transactions crashed with KeyError: 'type' on tx['type'], and code that printed tx['merchant']['name'] failed the same way. The first "fix", tx.get('type', 'unknown'), stopped the crash but labelled every transaction "Unknown".
Cause: v2 transactions (GET /transactions, GET /accounts/{id}/transactions, GET /transactions/{id}) have no type field and no nested merchant. In 300 live transactions, 0 had a "type" key and 0 had a "merchant" key. The spec's TransactionDTO requires id, kind, status, medium, amount_cents, settle_at, created_at, updated_at. - kind: deposit, withdrawal, transfer, purchase, bill_payment, fee, interest_credit, refund, chargeback - status: pending, completed, declined, cancelled - medium: balance, rewards - optional per kind: merchant_id (purchases, an id only; resolve the name with GET /merchants/{id}), payee_id (transfers), parent_transaction_id (refunds and chargebacks), decision / decision_reason / decision_source
Fix: switch on kind, and validate with a discriminated union so a wrong field name fails loudly instead of defaulting:
from typing import Annotated, Literal, Optional, Union from pydantic import BaseModel, Field, TypeAdapter class Base(BaseModel): id: str status: Literal["pending", "completed", "declined", "cancelled"] medium: Literal["balance", "rewards"] amount_cents: int payer_id: Optional[str] = None class Purchase(Base): kind: Literal["purchase"] merchant_id: Optional[str] = None class Transfer(Base): kind: Literal["transfer"] payee_id: Optional[str] = None class Reversal(Base): kind: Literal["refund", "chargeback"] parent_transaction_id: Optional[str] = None class Other(Base): kind: Literal["deposit", "withdrawal", "bill_payment", "fee", "interest_credit"] Tx = Annotated[Union[Purchase, Transfer, Reversal, Other], Field(discriminator="kind")] txs = TypeAdapter(list[Tx]).validate_python(resp.json()["items"] or [])
Checked with pydantic 2.x against 300 live transactions: all parsed. An unknown kind raises union_tag_invalid naming the expected tags.
In v2, purchases, deposits, transfers, fees and so on are all rows in one transaction ledger, distinguished only by kind.