> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperprop.com/llms.txt > Use this file to discover all available pages before exploring further. # Turn an account back on > Turns an `inactive` account back on. It returns to `in_progress` (or `not_started` if it never traded) with its balance, high-water mark, drawdown floor and trading days exactly as they were when it was turned off. The daily loss baseline resets at the next session as usual. **Billing:** if this trader has not been billed for the current calendar month (US Central time) yet, the month is billed now — the same charge an account that had stayed active would get. Live market data is switched back on. Only `inactive` accounts are turned back on. Repeating the call on an account that is already active is safe (`changed: false`, no webhook). `passed`, `failed` and `expired` accounts return **409**. Webhook: `account.status_changed` with `trigger: "firm_reactivated"`, `previousAttributes.status` and your `reason`. Requires **manage** permission on traders. On **502** retry the call — it is safe to repeat. ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/reactivate" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{"reason": "Trader is back"}' ``` ## OpenAPI ````yaml /api-reference/openapi.json post /v1/organization/trading-accounts/{accountId}/reactivate openapi: 3.0.0 info: title: Hyperprop Platform API version: 1.0.0 description: >- REST API for the Hyperprop Trading Platform — provision evaluation and funded trading accounts, manage traders and plans, react to account lifecycle events via signed webhooks, and reconcile billing. Built for prop firms integrating from their own backend. Authentication, quick start, error handling, idempotency, pagination, custom metadata, webhooks, and the MCP connector are documented at https://docs.hyperprop.com. x-logo: url: https://app.hyperprop.com/logo-icon.svg altText: Hyperprop href: https://hyperprop.com servers: - url: https://api.hyperprop.com/platform description: Production security: [] tags: - name: Trading accounts description: Create, update, and inspect trading accounts. - name: Traders description: Look up and update the traders in your organization. - name: Trading plans description: Define the plans you sell. - name: Trading rules description: Define how accounts are evaluated. - name: Lockouts description: Pause and resume trading on an account. - name: Payouts description: Check payout eligibility and record payouts. - name: Purchases description: Purchases recorded for your organization. - name: Time Machine description: Restore accounts to an earlier trading day or instant. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history and real-time event stream. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance and plan economics. - name: Billing description: 'Your Hyperprop bill: activity, billing cycles, and forecasts.' - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: Manage your organization's API key. - name: Logs and health description: API request logs, the audit log, and integration health. - name: Organization profile description: Your organization's profile and logo. - name: Support description: Open and follow up on support tickets. - name: Partner access description: >- Read a trader's journal as an approved partner app, with the trader's own key. paths: /v1/organization/trading-accounts/{accountId}/reactivate: post: tags: - Trading accounts summary: Turn an account back on description: >- Turns an `inactive` account back on. It returns to `in_progress` (or `not_started` if it never traded) with its balance, high-water mark, drawdown floor and trading days exactly as they were when it was turned off. The daily loss baseline resets at the next session as usual. **Billing:** if this trader has not been billed for the current calendar month (US Central time) yet, the month is billed now — the same charge an account that had stayed active would get. Live market data is switched back on. Only `inactive` accounts are turned back on. Repeating the call on an account that is already active is safe (`changed: false`, no webhook). `passed`, `failed` and `expired` accounts return **409**. Webhook: `account.status_changed` with `trigger: "firm_reactivated"`, `previousAttributes.status` and your `reason`. Requires **manage** permission on traders. On **502** retry the call — it is safe to repeat. ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/trading-accounts/7c9e6679-7425-40de-944b-e07fc1f90ae7/reactivate" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{"reason": "Trader is back"}' ``` operationId: postV1OrganizationTradingaccountsAccountidReactivate parameters: - x-format: guid: true name: accountId in: path required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/Model817' responses: '200': description: Success - Account is turned back on content: '*/*': schema: $ref: '#/components/schemas/Model819' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: >- Forbidden - This account belongs to a different organization, or the caller lacks traders:manage content: '*/*': schema: $ref: '#/components/schemas/Model820' '404': description: Not Found - No account exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model821' '409': description: Conflict - The account is passed, failed or expired content: '*/*': schema: $ref: '#/components/schemas/Model822' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' '502': description: The change was not confirmed. Retry the call. content: '*/*': schema: $ref: '#/components/schemas/Model823' security: - X-API-Key: [] components: schemas: Model817: type: object properties: reason: type: string description: >- Why the account is turned back on. Recorded on the audit trail and the webhook. example: Trader is back maxLength: 200 x-convert: trim: true Model819: type: object properties: success: type: boolean example: true message: type: string example: Account turned back on data: $ref: '#/components/schemas/Model818' Model9: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Authentication required code: type: string description: Machine-readable error code — switch on this, not on message text example: UNAUTHORIZED Model820: type: object properties: statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: This account does not belong to your organization code: type: string example: ACCOUNT_NOT_IN_ORG Model821: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Trading account not found code: type: string example: ACCOUNT_NOT_FOUND Model822: type: object properties: statusCode: type: number example: 409 error: type: string example: Conflict message: type: string example: >- Only a turned-off account can be turned back on; this account is failed code: type: string example: ACCOUNT_NOT_PAUSABLE Model5: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 500 error: type: string example: Internal Server Error message: type: string example: An unexpected error occurred code: type: string description: Machine-readable error code — switch on this, not on message text example: INTERNAL_ERROR Model823: type: object properties: statusCode: type: number example: 502 error: type: string example: Bad Gateway message: type: string example: >- The trading engine did not confirm the change. Retry the call, it is safe to repeat. code: type: string example: ENGINE_UNAVAILABLE Model818: type: object properties: accountId: type: string example: 7c9e6679-7425-40de-944b-e07fc1f90ae7 x-format: guid: true accountNumber: type: string example: TL-50K-000123 status: type: string description: '`in_progress`, or `not_started` if the account never traded' example: in_progress previousStatus: type: string example: inactive changed: type: boolean description: >- False when the account was already active — nothing changed and no webhook was sent example: true ordersCancelled: type: number example: 0 positionsClosed: type: number example: 0 reason: type: string example: Trader is back monthBilled: type: boolean description: >- True when this call billed the current calendar month; false when it was already billed (or the account is not billable) example: true securitySchemes: X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key. Format: "hp_live_{key}". Organization admins manage the key in the dashboard. ```` ## Related topics - [Turn an account off (pause)](/platform-api/trading-accounts/turn-an-account-off-pause.md) - [Continuous futures](/guides/continuous-futures.md) - [Changelog](/changelog.md) - [List payouts for an account](/platform-api/payouts/list-payouts-for-an-account.md) - [Webhooks](/guides/webhooks.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.