Halt the organisation's algos
Stops every started instance of your organisation, in id order, then answers with how many were stopped (algos:manage) — count is 0 when nothing was started, so the call always has an answer. Each instance’s stop is its own change, read on its row.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
Required on every write: a URL-safe string of 1 to 64 characters from [A-Za-z0-9._~-] (a UUID fits), scoped to you. It names one operation on one record, ever: a retry replays the stored outcome (Idempotent-Replay: true) or attaches to the live one, and reuse on another record refuses 409 IDEMPOTENCY_KEY_REUSED. Missing or malformed, 400.
Request
Why — required on every change, at most 256 bytes of UTF-8.
The command's idempotency key, 1 to 64 characters of letters, digits, dot, underscore, tilde and hyphen; a replay restates the earlier answer.
Response
The halt as the platform recorded it: count started instances stopped (0 when none was), with the answering change's position and, on a replayed key, Idempotent-Replay.
The position as a decimal string — the last change this member had applied, orders, balance readings and algo instances included.
Never present since 0.3.3: every money value on this API states its own scale on the wire — a policy amount or cap since 0.3.3, an order's and an execution's since 0.3.2, a balance's since 0.3.1 — so a row is never served raw, whether or not this member holds the asset or instrument it references. Kept, deprecated, so a client generated from 0.3.2 still compiles; it goes at the next major.