> ## Documentation Index > Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt > Use this file to discover all available pages before exploring further. # List server-managed stops > Returns the server-managed stops for this account — the automatic breakeven moves and trailing stops the engine is running — with the phase each has reached and, where one is paused, the reason nothing is moving the stop. The venue-placed stop still protects the position while management is paused. ## OpenAPI ````yaml /partner-platform/openapi.json get /api/account/managed-exits openapi: 3.1.0 info: title: trdrs Engine API version: 1.1.0 description: >- ## API Reference This is the served OpenAPI contract for the trdrs engine: market data, trading and account routes for your firm's traders, trdrs Connect account-registration handoff, and preview challenge routes. See Quick Start for the first integration path: key setup, market config, chart data, Connect account registrations, idempotency, stream reconnects, and conformance. See Overview and API Standards for the cross-cutting contract rules. servers: - url: https://app.trdrs.co description: Production - url: / description: This engine security: [] tags: - name: Market data description: >- Symbol search and resolution, OHLCV history, quote snapshots, the server clock, and the live bar stream. Crypto rides each venue’s public feed; futures stream from the caller’s own connected Rithmic account. With none connected, futures requests answer 503 `feed_requires_connection`. - name: News description: >- Aggregated market news and the economic calendar, from licensed/open sources, keyword-tagged with futures roots at ingest. Platform-wide content (nothing per-user), admitted exactly like Market data: a licensed origin, a session, or a firm API key. Headlines page by published time, scope by instrument root, and stream live over SSE; thumbnails serve through the image proxy. - name: Trading description: >- The money surface: entries, exits, replaces, cancels, and position/account flattening. Every order-placing call uses `clientOrderId` as its idempotency key. - name: Account description: >- Reading a connected account. You do not create trading accounts here: a trader connects their own broker account (or creates a free demo account) in the app, and firms create evaluation accounts through the Partner API (Firm accounts → Create evaluation accounts) or register venue accounts through Connect (Create an account registration). Account state and the durable ledgers: balances, positions, working orders, fills, P&L history, and the live account stream. - name: Connect description: >- trdrs Connect account registration, for partner firms. Register an account you issued on your own venue — a pending account registration — with the trader’s sign-in email, optionally the venue account id and the login name your venue issued. The trader finds it waiting in the connect flow the moment they sign in with that email: the connect step is pre-filled with everything except the credential, which the trader always enters themselves. A registration never transmits a password and never grants access to anything before the trader’s own login succeeds. These routes answer a partner-scoped key only; a firm API key or a user session gets 401. Registrations expire after 30 days; re-registering the same email + account refreshes the expiry instead of duplicating. The end-to-end flow guide is **[Quick Start](/docs/guides/quick-start)**. - name: Firm accounts description: >- Evaluation accounts your firm issues on the trdrs venue, through your partner key — the other half of account setup. Connect registrations hand off accounts that exist on your venue; these routes create and manage accounts on ours: the trader trades them on trdrs, and your firm owns the lifecycle. Every route is scoped to accounts your firm created through this API — an account the same trader opened themselves is invisible and untouchable here, by construction. Creation is batched with per-item results, and every write carries your own `referenceId`, so a crashed pipeline retries safely. Served when the deployment runs the prop engine; without it, every route in this group answers `404`. - name: Webhooks description: >- The outbound event bus: register an https endpoint and the platform pushes events to it instead of your back office polling us. Every delivery is signed (`trdrs-signature: t=,v1=` over `${t}.${rawBody}`) so you can prove it came from us and is fresh, and every delivery is durable — a failed attempt is retried with backoff for about nine hours and the whole log is readable, so an endpoint that was down is a delay rather than a lost event. Serves brokers and prop firms alike: the account-registration (`registration.*`) events fire wherever Connect does, and the account events fire where the prop engine runs. - name: Challenges description: >- The prop evaluation surface: challenge programs and a trader’s own enrollments. **Preview: the one group on this page outside the additive-only guarantee** (the pre-contract v1 scaffold; the Phase-1 rebuild will change these shapes; see Stability). **Cookie-authenticated, not key-authenticated**, and served only when the engine runs with `CHALLENGES_ENABLED`; without that flag the bundle is absent and every route below returns `404`. The firm-console/admin half of this surface is deliberately not documented here. It is back office, not licensed surface. paths: /api/account/managed-exits: get: tags: - Account summary: List server-managed stops description: >- Returns the server-managed stops for this account — the automatic breakeven moves and trailing stops the engine is running — with the phase each has reached and, where one is paused, the reason nothing is moving the stop. The venue-placed stop still protects the position while management is paused. parameters: - name: broker in: query schema: type: string - name: account in: query schema: type: string responses: '200': description: The server-managed stops content: application/json: schema: $ref: '#/components/schemas/ManagedExitsResponse' '401': description: Missing/unknown/revoked credential content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - tenantKey: [] x-codeSamples: - lang: javascript label: TypeScript source: >- const res = await fetch('https://app.trdrs.co/api/account/managed-exits', { headers: { Authorization: `Bearer ${process.env.TRDRS_API_KEY}` }, }) const data = await res.json() - lang: shell label: cURL source: |- curl 'https://app.trdrs.co/api/account/managed-exits' \ -H "Authorization: Bearer $TRDRS_API_KEY" components: schemas: ManagedExitsResponse: type: object properties: revision: type: integer description: >- The account revision these rows were read at. It is the current number, read rather than allocated: this one-shot read never advances the revision sequence the account's streams follow. items: type: array items: $ref: '#/components/schemas/ManagedExit' required: - revision - items example: revision: 412 items: - id: 9d2b6a30-4e17-4c85-b0f3-6a1c8e5d7204 accountId: 7a1f4c93b28d05e6f1a3c7d9b4e28f60 bracketId: b41e7d2a-9c58-4f03-a6b1-2e8d5c7f0a94 planId: 0f6c2d18-7b4a-4a3e-9d21-8c5e4b0a9f37 planRevision: q2Jm4XxT0aVnR7cLp1sZfE9d instrument: ESU6 side: buy state: pending phase: awaiting_entry actionable: true stopLevel: null targetLevels: - 6485.5 relatedOrderIds: - '234992187' pauseReason: null failureReason: null asOfRevision: 4831 ErrorResponse: type: object properties: error: type: string required: - error example: error: invalid_instrument ManagedExit: type: object description: >- WireManagedExit (@trdrs/contracts): one exit the engine is actively managing — a breakeven move, a trailing stop, or both. `paused` is honest degradation rather than failure: the last acknowledged stop is still resting at the venue, and `pauseReason` says why nothing is moving it. `planId` and `planRevision` are a receipt for the revision this instance accepted; the definition it runs was frozen then, so editing the saved plan cannot reach an already-open position. properties: id: type: string accountId: type: string bracketId: type: - string - 'null' planId: type: - string - 'null' planRevision: type: - string - 'null' instrument: type: string side: type: string enum: - buy - sell state: type: string enum: - pending - managing - paused - completed - cancelled - failed phase: type: string enum: - awaiting_entry - protecting - breakeven - trailing - done actionable: type: boolean stopLevel: type: - number - 'null' targetLevels: type: array items: type: number relatedOrderIds: type: array items: type: string pauseReason: type: - string - 'null' enum: - venue_disconnected - no_price_feed - no_instrument_facts - unsupported_shape - account_locked - null failureReason: type: - string - 'null' asOfRevision: type: integer required: - id - accountId - instrument - side - state - phase - actionable - targetLevels - relatedOrderIds - asOfRevision example: id: 9d2b6a30-4e17-4c85-b0f3-6a1c8e5d7204 accountId: 7a1f4c93b28d05e6f1a3c7d9b4e28f60 bracketId: b41e7d2a-9c58-4f03-a6b1-2e8d5c7f0a94 planId: 0f6c2d18-7b4a-4a3e-9d21-8c5e4b0a9f37 planRevision: q2Jm4XxT0aVnR7cLp1sZfE9d instrument: ESU6 side: buy state: pending phase: awaiting_entry actionable: true stopLevel: null targetLevels: - 6485.5 relatedOrderIds: - '234992187' pauseReason: null failureReason: null asOfRevision: 4831 securitySchemes: tenantKey: type: http scheme: bearer description: >- Your firm’s API key (the API calls this the `tenant` key; `trdrs_sk_…`), server-to-server only. ````