> ## 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. # Advance an account past a stage > Private preview, disabled unless VENUE_CONFIGURATION_ENABLED is enabled and the vault is configured. This branch has not enabled these routes in the public sandbox. Existing trdrs_sk partner/tenant keys do not authorize these routes. Requires stage:advance. Re-decides eligibility, then issues ONE successor for this source cycle and stage - a second attempt with a different idempotency key returns the account the first one made, because an account once issued cannot be un-issued. The policy must still be the exact version the decision was made under, the account's revision must not have moved since, and the account must be provably quiet. `startingAllocation` is required and null is a real value meaning a zero-balance successor. Only for accounts whose balance authority is TRDRS. A refusal returns 409 `not_eligible` with every failing reason. ## OpenAPI ````yaml /partner-platform/openapi.json post /api/partner/venues/{venueId}/accounts/{accountId}/stages/{stageId}/advance 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: Venue platform preview description: >- Disabled private-preview venue configuration APIs. VENUE_CONFIGURATION_ENABLED and a vault are required. Every route documented here under /api/partner/ is also served under /api/operator/ to a verified owner session, by the same router with a different credential: a browser must never hold a venue key, so an operator console reaches the identical checks that way rather than through a second copy of this surface. Not part of the stable public contract until qualification and release; existing partner APIs remain unchanged. - 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/partner/venues/{venueId}/accounts/{accountId}/stages/{stageId}/advance: post: tags: - Venue platform preview summary: Advance an account past a stage description: >- Private preview, disabled unless VENUE_CONFIGURATION_ENABLED is enabled and the vault is configured. This branch has not enabled these routes in the public sandbox. Existing trdrs_sk partner/tenant keys do not authorize these routes. Requires stage:advance. Re-decides eligibility, then issues ONE successor for this source cycle and stage - a second attempt with a different idempotency key returns the account the first one made, because an account once issued cannot be un-issued. The policy must still be the exact version the decision was made under, the account's revision must not have moved since, and the account must be provably quiet. `startingAllocation` is required and null is a real value meaning a zero-balance successor. Only for accounts whose balance authority is TRDRS. A refusal returns 409 `not_eligible` with every failing reason. parameters: - name: venueId in: path required: true schema: type: string format: uuid - name: accountId in: path required: true schema: type: string - name: stageId in: path required: true schema: type: string - name: Idempotency-Key in: header required: true schema: type: string minLength: 1 maxLength: 128 requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/VenueStageAdvanceRequest' responses: '200': description: 'Scoped result. Cache-Control: no-store.' content: application/json: schema: $ref: '#/components/schemas/VenueStageAdvanceResponse' '400': description: Invalid input, cursor or required request/version header. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Required credential missing or invalid. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: >- Verified identity, current owner membership or required scope missing. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Disabled feature, unavailable resource or wrong venue/environment. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Changed idempotent request or stale version. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '413': description: Request exceeds the bounded body size. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '415': description: JSON body required. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Service or credential vault unavailable; no success is implied. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - venueOperatorKey: [] x-codeSamples: - lang: javascript label: TypeScript source: >- const res = await fetch('https://app.trdrs.co/api/partner/venues/{venueId}/accounts/{accountId}/stages/{stageId}/advance', { method: 'POST', headers: { 'content-type': 'application/json', Authorization: `Bearer ${process.env.TRDRS_VENUE_KEY}`, "Idempotency-Key": "example-request-1", }, body: JSON.stringify({ "startingAllocation": { "numerator": "10000000", "denominator": "100" } }), }) const data = await res.json() - lang: shell label: cURL source: >- curl -X POST 'https://app.trdrs.co/api/partner/venues/{venueId}/accounts/{accountId}/stages/{stageId}/advance' \ -H "Authorization: Bearer $TRDRS_VENUE_KEY" \ -H 'Idempotency-Key: example-request-1' \ -H 'content-type: application/json' \ -d '{"startingAllocation":{"numerator":"10000000","denominator":"100"}}' components: schemas: VenueStageAdvanceRequest: type: object additionalProperties: false properties: startingAllocation: oneOf: - $ref: '#/components/schemas/VenueRational' - type: 'null' required: - startingAllocation example: startingAllocation: numerator: '10000000' denominator: '100' VenueStageAdvanceResponse: type: object additionalProperties: false properties: advance: $ref: '#/components/schemas/VenueStageAdvance' required: - advance example: advance: state: advanced targetAccountId: funded-account-1 cycleId: cycle:2026-09-14T12:00:00.000Z stageId: evaluation-1 policyId: 00000000-0000-0000-0000-000000000001 transitionReference: stage-9f1c2b7e4a5d80361c2b7e4a5d803612 ErrorResponse: type: object properties: error: type: string required: - error example: error: invalid_instrument VenueRational: type: object additionalProperties: false properties: numerator: type: string denominator: type: string required: - numerator - denominator description: >- An exact fraction of integers as decimal strings. Money is carried this way until it is posted, so nothing rounds twice on the way to the journal. VenueStageAdvance: type: object additionalProperties: false properties: state: type: string enum: - advanced - reserved targetAccountId: type: string cycleId: type: string stageId: type: string policyId: type: string format: uuid transitionReference: type: string required: - state - targetAccountId - cycleId - stageId - policyId - transitionReference description: >- `reserved` means the successor was named and created but its opening allocation has not been confirmed; `advanced` means it has. The two stay distinct because creation may one day happen at a provider, where "we asked" and "it exists" are different facts. securitySchemes: venueOperatorKey: type: http scheme: bearer description: >- Private-preview venue operator key (trdrs_vk_sandbox_… or trdrs_vk_production_…). Bound to one venue/environment and explicit scopes. Issued by a verified owner session; accepted only on documented /api/partner/venues/{venueId} routes. Existing trdrs_sk keys are not interchangeable. Never grants trader, login or key-management authority. ````