> ## 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. # Get a specific trader > Get detailed information about a specific trader in your organization. The `traderId` is the **Hyperprop user ID** (the `userId` field from the GET /organization/traders list). **What you get:** - User info (email, registration date, last sign in) - Profile info (username, avatar, etc.) - Organization metadata for this trader - Account statistics (total, active, passed, failed) - Full list of all their trading accounts with details **Example:** ```bash curl "https://api.hyperprop.com/platform/v1/organization/traders/{userId}" \ -H "X-API-Key: hp_live_your_key_here" ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/traders/{traderId} 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/traders/{traderId}: get: tags: - Traders summary: Get a specific trader description: >- Get detailed information about a specific trader in your organization. The `traderId` is the **Hyperprop user ID** (the `userId` field from the GET /organization/traders list). **What you get:** - User info (email, registration date, last sign in) - Profile info (username, avatar, etc.) - Organization metadata for this trader - Account statistics (total, active, passed, failed) - Full list of all their trading accounts with details **Example:** ```bash curl "https://api.hyperprop.com/platform/v1/organization/traders/{userId}" \ -H "X-API-Key: hp_live_your_key_here" ``` operationId: getV1OrganizationTradersTraderid parameters: - description: The Hyperprop user ID (from GET /organization/traders list) x-format: guid: true name: traderId in: path required: true schema: type: string responses: '200': description: Trader retrieved successfully content: '*/*': schema: $ref: '#/components/schemas/Model318' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Forbidden - Trader belongs to different org content: '*/*': schema: $ref: '#/components/schemas/Model319' '404': description: Not Found - Trader not found content: '*/*': schema: $ref: '#/components/schemas/Model320' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model318: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model317' 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 Model319: type: object properties: statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: This trader does not belong to your organization code: type: string example: TRADER_NOT_IN_ORG Model320: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Trader not found code: type: string example: TRADER_NOT_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 Model317: type: object example: userId: f994bc02-343c-4026-8a57-afc085eca8d5 email: trader@example.com emailVerified: true lastSignIn: '2026-02-17T12:57:40.301Z' registeredAt: '2026-01-02T11:29:46.700Z' joinedAt: '2026-01-26T16:57:42.850Z' metadata: customerTier: gold vip: true profile: username: johntrader displayName: John Trader name: John avatarUrl: https://api.dicebear.com/9.x/glass/svg?seed=john isPublic: true accounts: total: 5 active: 2 passed: 2 failed: 1 accountsList: - id: 7c9e6679-7425-40de-944b-e07fc1f90ae7 accountNumber: ACC-MKVEUQWQ type: evaluation status: in_progress initialBalance: 50000 currentBalance: 52000 highWaterMark: 52500 startedAt: '2026-02-01T09:00:00.000Z' completedAt: null violationReason: null metadata: source: website purchase: purchaseDate: '2026-01-28T10:00:00.000Z' pricePaid: 299 currency: USD createdAt: '2026-01-28T10:00:00.000Z' updatedAt: '2026-02-17T14:30:00.000Z' properties: userId: type: string email: type: string emailVerified: type: boolean lastSignIn: type: string registeredAt: type: string joinedAt: type: string metadata: $ref: '#/components/schemas/changes' profile: $ref: '#/components/schemas/Model313' accounts: $ref: '#/components/schemas/Model314' accountsList: $ref: '#/components/schemas/accountsList' changes: type: object Model313: type: object properties: username: type: string displayName: type: string name: type: string avatarUrl: type: string isPublic: type: boolean Model314: type: object properties: total: type: number active: type: number passed: type: number failed: type: number accountsList: type: array items: $ref: '#/components/schemas/Model316' Model316: type: object properties: id: type: string accountNumber: type: string type: type: string status: type: string initialBalance: type: number currentBalance: type: number highWaterMark: type: number startedAt: type: string completedAt: type: string violationReason: type: string metadata: $ref: '#/components/schemas/changes' purchase: $ref: '#/components/schemas/Model315' createdAt: type: string updatedAt: type: string Model315: type: object properties: purchaseDate: type: string pricePaid: type: number currency: type: string 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 - [Get a specific trading account](/platform-api/trading-accounts/get-a-specific-trading-account.md) - [Get a specific trading rule](/platform-api/trading-rules/get-a-specific-trading-rule.md) - [Get a specific purchase](/platform-api/purchases/get-a-specific-purchase.md) - [Get a specific trading plan](/platform-api/trading-plans/get-a-specific-trading-plan.md) - [Get traders for your organization](/platform-api/traders/get-traders-for-your-organization.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.