> ## 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 trading plan > Retrieve complete details for a single trading plan by its ID. **When to use this:** - Display plan details on a checkout page - Verify plan configuration before creating an account - Show plan info in your admin dashboard **What you get:** - Full plan details (name, price, duration, account size) - Complete trading rules attached to this plan - Custom metadata you've stored - Active/inactive status **Example:** ```http GET /organization/trading-plans/550e8400-e29b-41d4-a716-446655440000 ``` ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/trading-plans/{planId} 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-plans/{planId}: get: tags: - Trading plans summary: Get a specific trading plan description: |- Retrieve complete details for a single trading plan by its ID. **When to use this:** - Display plan details on a checkout page - Verify plan configuration before creating an account - Show plan info in your admin dashboard **What you get:** - Full plan details (name, price, duration, account size) - Complete trading rules attached to this plan - Custom metadata you've stored - Active/inactive status **Example:** ```http GET /organization/trading-plans/550e8400-e29b-41d4-a716-446655440000 ``` operationId: getV1OrganizationTradingplansPlanid parameters: - description: The plan ID to retrieve x-format: guid: true name: planId in: path required: true schema: type: string responses: '200': description: Success - Returns the trading plan content: '*/*': schema: $ref: '#/components/schemas/Model344' '401': description: Unauthorized - Invalid or missing API key content: '*/*': schema: $ref: '#/components/schemas/Model345' '403': description: Forbidden - This plan belongs to a different organization content: '*/*': schema: $ref: '#/components/schemas/Model346' '404': description: Not Found - No plan exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model347' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model344: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model343' Model345: type: object properties: statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Invalid or expired session Model346: type: object properties: statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: This plan does not belong to your organization code: type: string example: PLAN_NOT_IN_ORG Model347: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Trading plan not found code: type: string example: PLAN_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 Model343: type: object example: id: 09c93da5-f057-4cc5-82da-ff9220292c94 name: 50K Challenge description: >- Our most popular evaluation. Standard risk rules with a solid balance of target and protection. price: 299 currency: USD durationDays: 30 accountSize: 50000 isActive: true metadata: targetAudience: beginner internalCode: PLAN-50K-V2 tradingRule: id: 6bec94a1-425b-47be-bb41-a80e3140e2e7 name: Standard Rules description: >- Balanced evaluation rules with 8% profit target and 5% max trailing loss. profitTarget: 4000 dailyProfit: 0 maxProfit: 0 dailyLoss: 1000 maxLoss: 2500 dailyDrawdown: 2 maxDrawdown: 5 drawdownType: static consistency: 0 maxContracts: 10 microConversionRatio: 10 createdAt: '2025-12-30T12:28:04.204Z' updatedAt: '2025-12-30T12:28:04.204Z' properties: id: type: string description: Unique plan ID name: type: string description: Plan display name description: type: string description: Plan description price: type: number description: Plan price currency: type: string description: Price currency durationDays: type: number description: Evaluation period in days accountSize: type: number description: Starting account balance isActive: type: boolean description: Whether this plan can be purchased metadata: $ref: '#/components/schemas/Model341' tradingRule: $ref: '#/components/schemas/Model342' createdAt: type: string updatedAt: type: string Model341: type: object description: Custom metadata Model342: type: object description: Trading rules for this plan properties: id: type: string name: type: string description: type: string profitTarget: type: number dailyProfit: type: number maxProfit: type: number dailyLoss: type: number maxLoss: type: number dailyDrawdown: type: number maxDrawdown: type: number consistency: type: number maxContracts: type: number description: >- Max position size in mini-equivalent contracts. On a market whose contract steps fractionally (the BTCUSDT perpetual steps 0.001 BTC) this counts ENGINE units, so 100 is 0.1 BTC and 1000 is 1 BTC — read `quantityStep` on the contract rather than assuming one unit is one coin. microConversionRatio: type: number description: How many micros count as 1 unit toward maxContracts (default 10) maxPositionByMarket: $ref: '#/components/schemas/maxPositionByMarket' maxPositionByMarket: type: object description: >- Per-market position limits in each market's own unit. Overrides maxContracts for the markets it names. example: BINANCE: 0.5 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 trading plans for your organization](/platform-api/trading-plans/get-trading-plans-for-your-organization.md) - [Get a specific purchase](/platform-api/purchases/get-a-specific-purchase.md) - [Get purchases for your organization](/platform-api/purchases/get-purchases-for-your-organization.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.