> ## 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. # Reset a team member's password > Use this when a staff member is locked out or forgot their password. - **A login your organization created:** a new strong temporary password is generated and returned **once** (`delivery: "response"`) — copy it and share it securely. The member should change it after signing in (Settings → Security). - **A login the person had before joining your team:** no password is set or returned. The member is emailed a link to choose a new password (`delivery: "email"`, `tempPassword: null`). You cannot reset your own password here — use the normal password change flow instead. You cannot reset the password of someone whose role has more access than yours (403 ROLE_ABOVE_YOURS). **Permissions:** requires **manage** access to "Team & roles". **Authentication:** send your organization API key in the `X-API-Key` header. **Access:** full-access API keys only (a read-only key gets `403 READ_ONLY_KEY`). Dashboard members need manage access to Team & roles. ## OpenAPI ````yaml https://api.hyperprop.com/platform/openapi.json post /v1/organization/team/{memberId}/reset-password 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: Instruments description: >- The contracts your organization's accounts can trade, with their specifications. - 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: Mass credit description: >- Credit back losses across many accounts after an incident, as background jobs you can follow, pause, export and reverse. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history, to replay or audit what happened. - name: Real-time streams description: >- Live events and trading data over a WebSocket, for dashboards and CRMs that update as things happen. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance, revenue and top traders. - name: Risk description: Firm profit and loss and plan economics. - name: Billing and invoices description: >- Your Hyperprop invoices, credits and billing details, with usage so far this month, billing cycles, forecasts and CSV exports. - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: >- Manage your organization's API keys: rotation, read-only keys and IP allowlists. - name: Logs and health description: >- API request logs, the audit log, integration health, and idempotency key recovery. - 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/team/{memberId}/reset-password: post: tags: - Team and roles summary: Reset a team member's password description: >- Use this when a staff member is locked out or forgot their password. - **A login your organization created:** a new strong temporary password is generated and returned **once** (`delivery: "response"`) — copy it and share it securely. The member should change it after signing in (Settings → Security). - **A login the person had before joining your team:** no password is set or returned. The member is emailed a link to choose a new password (`delivery: "email"`, `tempPassword: null`). You cannot reset your own password here — use the normal password change flow instead. You cannot reset the password of someone whose role has more access than yours (403 ROLE_ABOVE_YOURS). **Permissions:** requires **manage** access to "Team & roles". **Authentication:** send your organization API key in the `X-API-Key` header. **Access:** full-access API keys only (a read-only key gets `403 READ_ONLY_KEY`). Dashboard members need manage access to Team & roles. operationId: postV1OrganizationTeamMemberidResetpassword parameters: - description: Team member user ID x-format: guid: true name: memberId in: path required: true example: 55555555-5555-4555-8555-555555555555 schema: type: string - name: Idempotency-Key in: header required: false description: >- Optional. A value that identifies this operation on your side, at most 255 characters. A retry with the same key, method, path and body within 24 hours returns the original response (with `Idempotency-Replayed: true`) instead of repeating the change. The same key with a different body returns `409 IDEMPOTENCY_KEY_REUSED`; a retry while the first request is still running returns `409 IDEMPOTENCY_KEY_IN_PROGRESS`. Server errors (5xx) are not saved, so a retry runs again. example: crm-sync-8814-attempt-1 schema: type: string maxLength: 255 responses: '200': description: New temporary password (shown once), or a reset email sent content: application/json: schema: $ref: '#/components/schemas/Model1384' '400': description: >- The request does not match the documented parameters or body; `message` names the field content: application/json: schema: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: integer example: 400 error: type: string example: Bad Request message: type: string example: '"limit" must be less than or equal to 100' code: type: string enum: - VALIDATION_ERROR example: VALIDATION_ERROR description: >- Machine-readable error code — switch on this, not on message text '401': description: Missing, invalid or revoked API key content: application/json: schema: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: integer example: 401 error: type: string example: Unauthorized message: type: string example: Invalid or missing API key code: type: string enum: - UNAUTHORIZED example: UNAUTHORIZED description: >- Machine-readable error code — switch on this, not on message text '403': description: Access denied content: application/json: schema: $ref: '#/components/schemas/Model74' '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/Model32' '409': description: >- The `Idempotency-Key` was used with a different body (`IDEMPOTENCY_KEY_REUSED`), or a request with the same key is still running (`IDEMPOTENCY_KEY_IN_PROGRESS`) content: application/json: schema: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: integer example: 409 error: type: string example: Conflict message: type: string example: >- This Idempotency-Key was already used with a different request body. Use a new key for a different request. code: type: string enum: - IDEMPOTENCY_KEY_REUSED - IDEMPOTENCY_KEY_IN_PROGRESS example: IDEMPOTENCY_KEY_REUSED description: >- Machine-readable error code — switch on this, not on message text '500': description: An unexpected error occurred content: application/json: schema: $ref: '#/components/schemas/Model6' security: - X-API-Key: [] components: schemas: Model1384: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model1383' Model74: 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 Model32: 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: Resource not found code: type: string description: Machine-readable error code — switch on this, not on message text example: NOT_FOUND Model6: 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 Model1383: type: object properties: id: type: string email: type: string example: sarah@example.com tempPassword: type: string description: >- Shown ONCE — share securely. Null when a reset email was sent instead. example: Tn6w-Pk3r-Vx9c-Db4m delivery: $ref: '#/components/schemas/delivery' delivery: type: string description: >- response: the temporary password is in this response. email: the member was emailed a reset link. example: response enum: - response - email securitySchemes: X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key (`hp_live_...`), sent in the `X-API-Key` header. Create, rotate and restrict keys in the dashboard or with the API keys endpoints; an organization can have two active keys, so you can rotate without downtime. A **full-access** key can call every endpoint in this reference. A **read-only** key can call `GET` endpoints (and create a trading stream token); any other request returns `403 READ_ONLY_KEY`. A key with an IP allowlist returns `403 IP_NOT_ALLOWED` from any other address. Each endpoint lists which keys can call it under **Access**. ```` ## Related topics - [Team and roles](https://docs.hyperprop.com/guides/team-and-roles.md) - [Add a team member with a role](https://docs.hyperprop.com/platform-api/team-and-roles/add-a-team-member-with-a-role.md) - [Remove a team member](https://docs.hyperprop.com/platform-api/team-and-roles/remove-a-team-member.md) - [Rebind a customer to a new Hyperprop login (support flow)](https://docs.hyperprop.com/platform-api/traders/rebind-a-customer-to-a-new-hyperprop-login-support-flow.md) - [Change a team member's role](https://docs.hyperprop.com/platform-api/team-and-roles/change-a-team-members-role.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.