Wallets

Reset Wallet

Archive the current wallet and spawn the next-generation copy.

Behaviour (spec §8):

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.

First-PR scope: SANDBOX only. MAIN reset uses the existing /reset-account flow (cooldown-gated, with full account_reset_backups snapshot) — that path is out of scope here. API reset uses /v1/account/reset-api-balance. COMPETITION is runner-only.

No emergency-exit step is needed yet: SANDBOX wallets do not own positions until the per-wallet routing PR. Once that lands, this endpoint must close open SANDBOX positions before archiving.

D1 — wrap in the per-user advisory lock so a concurrent SANDBOX reset + place-trade for the same user serialize at the application layer instead of contending on the wallets/accounts FOR UPDATE. Reset emits LedgerEntry rows against user.account.id and spawns a fresh wallet row; holding the lock across the body prevents a trade-vs-reset race. See PR #1208 for the original advisory-lock landing.

POST

/

v1

/

me

/

wallets

/

{wallet_id}

/

reset

Reset Wallet

curl --request POST \
  --url https://api.polysimulator.com/v1/me/wallets/{wallet_id}/reset \
  --header 'X-API-Key: <api-key>'

{
  "id": 123,
  "kind": "<string>",
  "label": "<string>",
  "balance": "<string>",
  "baseline": "<string>",
  "status": "<string>",
  "generation": 123,
  "parent_wallet_id": 123,
  "competition_id": 123,
  "created_at": "<string>",
  "archived_at": "<string>",
  "is_legacy": false,
  "managed_by": {
    "tenant_slug": "<string>",
    "display_name": "<string>"
  },
  "b2b_account": {
    "account_id": "<string>",
    "stage": "<string>",
    "status": "<string>"
  }
}

Authorizations

X-API-Key

string

header

required

Issue from /v1/keys (or admin-issued for enterprise tier).

Headers

authorization

string | null

X-API-Key

string | null

POLY_API_KEY

string | null

Poly-API-Key

string | null

Path Parameters

wallet_id

integer

required

Response

Successful Response

id

integer

required

kind

string

required

label

string | null

required

balance

string

required

baseline

string

required

status

string

required

generation

integer

required

parent_wallet_id

integer | null

required

competition_id

integer | null

required

created_at

string | null

required

archived_at

string | null

required

is_legacy

boolean

default:false

managed_by

WalletManagedByOut · object

Tenant identity for a PROP_FIRM wallet (prop-firm plan §8 managed_by). Drives the native Managed by {display_name} label.

Show child attributes

b2b_account

WalletB2BAccountOut · object

Governance-account summary for a PROP_FIRM wallet (prop-firm plan §8 b2b_account). account_id is the UUID as a string; stage is one of demo|challenge|funded (rendered as the Demo/Challenge/Funded badge); status one of active|closed|archived.

Show child attributes

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.

Reset Wallet

curl --request POST \
  --url https://api.polysimulator.com/v1/me/wallets/{wallet_id}/reset \
  --header 'X-API-Key: <api-key>'

{
  "id": 123,
  "kind": "<string>",
  "label": "<string>",
  "balance": "<string>",
  "baseline": "<string>",
  "status": "<string>",
  "generation": 123,
  "parent_wallet_id": 123,
  "competition_id": 123,
  "created_at": "<string>",
  "archived_at": "<string>",
  "is_legacy": false,
  "managed_by": {
    "tenant_slug": "<string>",
    "display_name": "<string>"
  },
  "b2b_account": {
    "account_id": "<string>",
    "stage": "<string>",
    "status": "<string>"
  }
}