Wallets
Reset Wallet
Archive the current wallet and spawn the next-generation copy.
Behaviour:
- Old wallet: status=ARCHIVED, archived_at=NOW; LedgerEntry(RESET)
emitted on the user’s accounts row as a forensic boundary marker
(reference_id=
wallet:{old_id}:reset). - New wallet: same kind, generation=N+1, parent_wallet_id=old_id,
balance=baseline (from FEATURE_MATRIX), status=ACTIVE; LedgerEntry
(DEPOSIT, baseline) emitted with reference_id=
wallet:{new_id}:init.
POST
Reset Wallet
Authorizations
Issue from /v1/keys (or admin-issued for enterprise tier).
Headers
Path Parameters
Response
Successful Response
Previous
Export Trades CsvExport the caller's FILLED trades as a streamed CSV.
Auth: dashboard session (Supabase JWT) **or** a ``ps_live_``/``ps_test_``
API key. FILLED-only (``status='FILLED'`` and ``filled_at IS NOT NULL``).
Keyset-paginated under the hood (``filled_at DESC, id DESC``) and streamed
in batches so deep histories don't materialise in memory. Capped at
``EXPORT_MAX_ROWS`` per request.
Next
Reset Wallet