> ## 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. # Bulk update trading accounts > Bulk update multiple trading accounts at once. **Admin only**. All changes are logged to the audit trail with the batch ID for easy tracking. **Filters (at least one required):** | Filter | Description | |--------|-------------| | `accountIds` | Specific account IDs to update | | `status` | Filter by current status | | `createdAfter` / `createdBefore` | Filter by creation date | | `startedAfter` / `startedBefore` | Filter by start timestamp | | `tradingPlanId` | Filter by trading plan | | `userId` | Filter by user ID | **Updates (at least one required):** | Update | Description | |--------|-------------| | `status` | Change status | | `currentBalance` | Set new balance | | `highWaterMark` | Set new high water mark | | `dailyStartingBalance` | Set new daily starting balance | | `violationReason` | Set or clear (null) violation reason | | `performanceData` | Replace performance data | | `metadata` | Replace metadata | | `resetToInitial` | Reset to initial balance + in_progress status | **Safety:** - A reason is required for all bulk updates - Max 100 accounts without specifying accountIds - All changes are logged with before/after values **Example - Reset failed accounts after outage:** ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/trading-accounts/bulk-update" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "filters": { "status": "failed", "startedAfter": "2026-01-15T14:00:00Z", "startedBefore": "2026-01-15T16:00:00Z" }, "updates": { "resetToInitial": true }, "reason": "Outage compensation" }' ``` **Example - Bulk fail accounts:** ```bash curl -X POST ".../bulk-update" \ -d '{ "filters": { "accountIds": ["id1", "id2", "id3"] }, "updates": { "status": "failed", "violationReason": "Terms of service violation" }, "reason": "ToS violation - detected automated trading" }' ``` **Error Codes:** | Code | Description | |------|-------------| | `REASON_REQUIRED` | Reason must be at least 3 characters | | `NO_ACCOUNTS_FOUND` | No accounts match the filters | | `TOO_MANY_ACCOUNTS` | Over 100 accounts without specific IDs | | `NO_FIELDS_TO_UPDATE` | No valid update fields provided | ## OpenAPI ````yaml /api-reference/openapi.json post /v1/organization/trading-accounts/bulk-update 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/bulk-update: post: tags: - Trading accounts summary: Bulk update trading accounts description: >- Bulk update multiple trading accounts at once. **Admin only**. All changes are logged to the audit trail with the batch ID for easy tracking. **Filters (at least one required):** | Filter | Description | |--------|-------------| | `accountIds` | Specific account IDs to update | | `status` | Filter by current status | | `createdAfter` / `createdBefore` | Filter by creation date | | `startedAfter` / `startedBefore` | Filter by start timestamp | | `tradingPlanId` | Filter by trading plan | | `userId` | Filter by user ID | **Updates (at least one required):** | Update | Description | |--------|-------------| | `status` | Change status | | `currentBalance` | Set new balance | | `highWaterMark` | Set new high water mark | | `dailyStartingBalance` | Set new daily starting balance | | `violationReason` | Set or clear (null) violation reason | | `performanceData` | Replace performance data | | `metadata` | Replace metadata | | `resetToInitial` | Reset to initial balance + in_progress status | **Safety:** - A reason is required for all bulk updates - Max 100 accounts without specifying accountIds - All changes are logged with before/after values **Example - Reset failed accounts after outage:** ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/trading-accounts/bulk-update" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "filters": { "status": "failed", "startedAfter": "2026-01-15T14:00:00Z", "startedBefore": "2026-01-15T16:00:00Z" }, "updates": { "resetToInitial": true }, "reason": "Outage compensation" }' ``` **Example - Bulk fail accounts:** ```bash curl -X POST ".../bulk-update" \ -d '{ "filters": { "accountIds": ["id1", "id2", "id3"] }, "updates": { "status": "failed", "violationReason": "Terms of service violation" }, "reason": "ToS violation - detected automated trading" }' ``` **Error Codes:** | Code | Description | |------|-------------| | `REASON_REQUIRED` | Reason must be at least 3 characters | | `NO_ACCOUNTS_FOUND` | No accounts match the filters | | `TOO_MANY_ACCOUNTS` | Over 100 accounts without specific IDs | | `NO_FIELDS_TO_UPDATE` | No valid update fields provided | operationId: postV1OrganizationTradingaccountsBulkupdate requestBody: content: application/json: schema: $ref: '#/components/schemas/Model682' responses: '200': description: Bulk update successful content: '*/*': schema: $ref: '#/components/schemas/Model684' '400': description: Bad Request content: '*/*': schema: $ref: '#/components/schemas/Model685' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Access denied content: '*/*': schema: $ref: '#/components/schemas/Model47' '404': description: No accounts match filters content: '*/*': schema: $ref: '#/components/schemas/Model686' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model682: type: object properties: filters: $ref: '#/components/schemas/Model678' updates: $ref: '#/components/schemas/updates' reason: type: string description: Reason for the bulk update (required for audit) example: Goodwill credit minLength: 3 required: - filters - updates - reason Model684: type: object properties: success: type: boolean example: true message: type: string example: Successfully updated 15 accounts data: $ref: '#/components/schemas/Model683' Model685: type: object properties: statusCode: type: number example: 400 error: type: string example: Bad Request message: type: string example: A reason is required for bulk updates code: type: string example: REASON_REQUIRED 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 Model47: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: Access denied code: type: string description: Machine-readable error code — switch on this, not on message text example: FORBIDDEN Model686: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: No accounts match the specified filters code: type: string example: NO_ACCOUNTS_FOUND 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 Model678: type: object description: Filters to select which accounts to update properties: accountIds: $ref: '#/components/schemas/Model676' status: $ref: '#/components/schemas/Model677' createdAfter: type: string description: Accounts created after this date x-format: isoDate: true createdBefore: type: string description: Accounts created before this date x-format: isoDate: true startedAfter: type: string description: Accounts started after this timestamp x-format: isoDate: true startedBefore: type: string description: Accounts started before this timestamp x-format: isoDate: true tradingPlanId: type: string description: Filter by trading plan x-format: guid: true userId: type: string description: Filter by user ID x-format: guid: true updates: type: object description: Updates to apply properties: status: $ref: '#/components/schemas/Model679' currentBalance: type: number description: New current balance highWaterMark: type: number description: New high water mark dailyStartingBalance: type: number description: New daily starting balance violationReason: type: string description: Set or clear violation reason performanceData: $ref: '#/components/schemas/Model680' metadata: $ref: '#/components/schemas/Model681' resetToInitial: type: boolean description: Reset accounts to initial balance and in_progress status Model683: type: object example: batchId: e4f5a6b7-c8d9-0123-efab-456789012345 accountsUpdated: 15 accountsTotal: 15 filters: status: failed startDate: '2026-02-01' updates: status: in_progress resetToInitial: true reason: Server maintenance compensation - resetting failed accounts properties: batchId: type: string description: Batch ID for tracking this operation x-format: guid: true accountsUpdated: type: number accountsTotal: type: number filters: $ref: '#/components/schemas/changes' updates: $ref: '#/components/schemas/changes' reason: type: string Model676: type: array description: Specific account IDs to update items: type: string x-format: guid: true Model677: type: string description: Filter by current status enum: - not_started - in_progress - passed - failed - expired Model679: type: string description: New status enum: - not_started - in_progress - passed - failed - expired Model680: type: object description: New performance data Model681: type: object description: New metadata (replaces existing) changes: type: object 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 - [Bulk update copy trading group followers](/trade-api/copy-trading/bulk-update-copy-trading-group-followers.md) - [Bulk revert accounts to a trading day or an instant](/platform-api/time-machine/bulk-revert-accounts-to-a-trading-day-or-an-instant.md) - [Update a trading account](/platform-api/trading-accounts/update-a-trading-account.md) - [Get bulk operation details](/platform-api/trading-accounts/get-bulk-operation-details.md) - [Bulk-create unlinked accounts with import keys](/platform-api/trading-accounts/bulk-create-unlinked-accounts-with-import-keys.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.