> ## 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. # Rebind a customer to a new Hyperprop login (support flow) > Move a soulbound customer to a **new** Hyperprop login in one atomic operation. There is no plain "release" — every customer always has exactly one bound login, so a lost login is fixed by rebinding, never by leaving the customer unbound. **Use this when a customer lost access to their Hyperprop login** (forgot password AND lost the email — normal password reset covers everything else): 1. Customer contacts YOUR support 2. The customer creates their new Hyperprop account (signs up) 3. You rebind here with the new login's `email` (or `traderId`) — find the binding via `GET /trader-bindings?customerId=...` **What happens:** - The binding now points at the new login (`boundVia: "rebind"`) - **Every still-active account (`not_started` / `in_progress`) linked to the OLD login is set to `failed`** with the violation reason "Identity rebound by the firm ..." — the old login can never trade this customer's accounts again. An `account.failed` webhook fires per account, and the old login's open trading sessions end immediately. - Terminal accounts (`passed`/`failed`/`expired`) are untouched — history stays with the old identity for audit. - Unlinked accounts with pending import keys are now redeemable **only** by the new login. - Give the customer new accounts by creating them for the new login (or unassigned with an import key) — failed accounts are not transferred. - **Billing note:** activating an account under the new login (redeeming a pending key, or a new linked create) counts as a fresh market data activation for that login — a new billing cycle (platform + market data) starts, on top of what the old login already consumed. Billing follows logins, not customers. **Safety checks:** - The new login must be an existing Hyperprop user (`404 TRADER_NOT_FOUND` otherwise — have the customer sign up first). - One login = one customer per firm: if the new login already belongs to a **different** customer of yours, the rebind is refused with `409 NEW_LOGIN_ALREADY_BOUND`. - Rebinding to the already-bound login is a no-op and returns `400 SAME_LOGIN`. **Permissions:** organization **admins** (or API key). Supports idempotency keys. **Error codes:** `BINDING_NOT_FOUND`, `TRADER_NOT_FOUND`, `SAME_LOGIN`, `NEW_LOGIN_ALREADY_BOUND`, `REBIND_ERROR`. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/organization/trader-bindings/{bindingId}/rebind 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/trader-bindings/{bindingId}/rebind: post: tags: - Traders summary: Rebind a customer to a new Hyperprop login (support flow) description: >- Move a soulbound customer to a **new** Hyperprop login in one atomic operation. There is no plain "release" — every customer always has exactly one bound login, so a lost login is fixed by rebinding, never by leaving the customer unbound. **Use this when a customer lost access to their Hyperprop login** (forgot password AND lost the email — normal password reset covers everything else): 1. Customer contacts YOUR support 2. The customer creates their new Hyperprop account (signs up) 3. You rebind here with the new login's `email` (or `traderId`) — find the binding via `GET /trader-bindings?customerId=...` **What happens:** - The binding now points at the new login (`boundVia: "rebind"`) - **Every still-active account (`not_started` / `in_progress`) linked to the OLD login is set to `failed`** with the violation reason "Identity rebound by the firm ..." — the old login can never trade this customer's accounts again. An `account.failed` webhook fires per account, and the old login's open trading sessions end immediately. - Terminal accounts (`passed`/`failed`/`expired`) are untouched — history stays with the old identity for audit. - Unlinked accounts with pending import keys are now redeemable **only** by the new login. - Give the customer new accounts by creating them for the new login (or unassigned with an import key) — failed accounts are not transferred. - **Billing note:** activating an account under the new login (redeeming a pending key, or a new linked create) counts as a fresh market data activation for that login — a new billing cycle (platform + market data) starts, on top of what the old login already consumed. Billing follows logins, not customers. **Safety checks:** - The new login must be an existing Hyperprop user (`404 TRADER_NOT_FOUND` otherwise — have the customer sign up first). - One login = one customer per firm: if the new login already belongs to a **different** customer of yours, the rebind is refused with `409 NEW_LOGIN_ALREADY_BOUND`. - Rebinding to the already-bound login is a no-op and returns `400 SAME_LOGIN`. **Permissions:** organization **admins** (or API key). Supports idempotency keys. **Error codes:** `BINDING_NOT_FOUND`, `TRADER_NOT_FOUND`, `SAME_LOGIN`, `NEW_LOGIN_ALREADY_BOUND`, `REBIND_ERROR`. operationId: postV1OrganizationTraderbindingsBindingidRebind parameters: - description: Binding ID from GET /trader-bindings x-format: guid: true name: bindingId in: path required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/Model739' responses: '200': description: Success - customer rebound to the new login content: '*/*': schema: $ref: '#/components/schemas/Model742' '400': description: This customer is already bound to that Hyperprop login content: '*/*': schema: $ref: '#/components/schemas/Model743' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Only organization admins can perform this action content: '*/*': schema: $ref: '#/components/schemas/Model570' '404': description: Binding not found in your organization content: '*/*': schema: $ref: '#/components/schemas/Model744' '409': description: That Hyperprop login already belongs to another customer of yours content: '*/*': schema: $ref: '#/components/schemas/Model745' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model739: type: object properties: traderId: type: string description: >- The NEW Hyperprop user ID to bind this customer to. Provide EITHER traderId OR email. example: f994bc02-343c-4026-8a57-afc085eca8d5 x-format: guid: true email: type: string description: >- Email of the customer's NEW Hyperprop login (must already exist — the customer signs up first). Resolved to their user ID server-side. example: customer-new@gmail.com x-format: email: true Model742: type: object properties: success: type: boolean example: true message: type: string example: Customer rebound — 2 active account(s) on the old login were failed data: $ref: '#/components/schemas/Model741' Model743: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 400 error: type: string example: Bad Request message: type: string example: This customer is already bound to that Hyperprop login code: type: string description: Machine-readable error code — switch on this, not on message text example: SAME_LOGIN 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 Model570: 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: Only organization admins can perform this action code: type: string description: Machine-readable error code — switch on this, not on message text example: NOT_ADMIN Model744: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Binding not found in your organization code: type: string description: Machine-readable error code — switch on this, not on message text example: BINDING_NOT_FOUND Model745: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 409 error: type: string example: Conflict message: type: string example: That Hyperprop login already belongs to another customer of yours code: type: string description: Machine-readable error code — switch on this, not on message text example: NEW_LOGIN_ALREADY_BOUND 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 Model741: type: object properties: binding: $ref: '#/components/schemas/binding' failedAccounts: $ref: '#/components/schemas/failedAccounts' binding: type: object properties: id: type: string organizationId: type: string customerId: type: string example: acme-cust-4471 userId: type: string description: The NEW Hyperprop user ID email: type: string description: The NEW Hyperprop login email example: customer-new@gmail.com boundAt: type: string x-format: isoDate: true boundVia: type: string example: rebind failedAccounts: type: array description: Still-active accounts of the old login that were failed by this rebind items: $ref: '#/components/schemas/Model740' Model740: type: object properties: id: type: string accountNumber: type: string example: ACC-M3X7K9P2 previousStatus: type: string example: in_progress 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 - [List trader identity bindings (customer ⇄ Hyperprop login)](/platform-api/traders/list-trader-identity-bindings-customer-⇄-hyperprop-login.md) - [Unlink a trader (issues a fresh import key)](/platform-api/trading-accounts/unlink-a-trader-issues-a-fresh-import-key.md) - [Create a trading account](/platform-api/trading-accounts/create-a-trading-account.md) - [Changelog](/changelog.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.