> ## 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 purchase > Retrieve complete details for a single purchase by its ID. **When to use this:** - Display purchase details in your admin dashboard - Look up a specific transaction for support - Verify payment details for refund processing - Track which accounts were created from a purchase **What you get:** - Purchase details (date, price, currency, status) - Full trading plan info - All accounts created from this purchase (with their current status) - Custom metadata (payment IDs, promo codes, etc.) **Example:** ```http GET /organization/purchases/f47ac10b-58cc-4372-a567-0e02b2c3d479 ``` **Understanding the response:** - `accounts` = All trading accounts created from this purchase - `tradingPlan` = The plan that was purchased (full details) - `metadata` = Any custom data you stored (payment IDs, promo codes, etc.) ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/purchases/{purchaseId} 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/purchases/{purchaseId}: get: tags: - Purchases summary: Get a specific purchase description: >- Retrieve complete details for a single purchase by its ID. **When to use this:** - Display purchase details in your admin dashboard - Look up a specific transaction for support - Verify payment details for refund processing - Track which accounts were created from a purchase **What you get:** - Purchase details (date, price, currency, status) - Full trading plan info - All accounts created from this purchase (with their current status) - Custom metadata (payment IDs, promo codes, etc.) **Example:** ```http GET /organization/purchases/f47ac10b-58cc-4372-a567-0e02b2c3d479 ``` **Understanding the response:** - `accounts` = All trading accounts created from this purchase - `tradingPlan` = The plan that was purchased (full details) - `metadata` = Any custom data you stored (payment IDs, promo codes, etc.) operationId: getV1OrganizationPurchasesPurchaseid parameters: - description: The purchase ID to retrieve x-format: guid: true name: purchaseId in: path required: true schema: type: string responses: '200': description: Success - Returns the purchase content: '*/*': schema: $ref: '#/components/schemas/Model272' '401': description: Unauthorized - Invalid or missing API key content: '*/*': schema: $ref: '#/components/schemas/Model273' '403': description: Forbidden - This purchase belongs to a different organization content: '*/*': schema: $ref: '#/components/schemas/Model274' '404': description: Not Found - No purchase exists with this ID content: '*/*': schema: $ref: '#/components/schemas/Model275' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model272: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model271' Model273: type: object properties: statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Invalid or expired session Model274: type: object properties: statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: This purchase does not belong to your organization code: type: string example: PURCHASE_NOT_IN_ORG Model275: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Purchase not found code: type: string example: PURCHASE_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 Model271: type: object example: id: f47ac10b-58cc-4372-a567-0e02b2c3d479 purchaseDate: '2026-01-28T10:00:00.000Z' startDate: '2026-01-28T10:00:00.000Z' endDate: '2026-02-27T10:00:00.000Z' status: paid pricePaid: 299 currency: USD metadata: stripePaymentId: pi_3ABC123 promoCode: SUMMER25 tradingPlan: id: 09c93da5-f057-4cc5-82da-ff9220292c94 name: 50K Challenge description: Our most popular evaluation. price: 299 currency: USD durationDays: 30 accountSize: 50000 accounts: - id: 7c9e6679-7425-40de-944b-e07fc1f90ae7 accountNumber: ACC-7845KXPQ status: in_progress initialBalance: 50000 currentBalance: 52150 startedAt: '2026-02-01T09:00:00.000Z' completedAt: null userId: f994bc02-343c-4026-8a57-afc085eca8d5 userEmail: trader@example.com createdAt: '2026-01-28T10:00:00.000Z' updatedAt: '2026-01-28T10:00:00.000Z' properties: id: type: string description: Unique purchase ID purchaseDate: type: string description: When the purchase was made startDate: type: string description: When the evaluation period started endDate: type: string description: When the evaluation period ends status: type: string description: Purchase status pricePaid: type: number description: Amount paid currency: type: string description: Payment currency metadata: $ref: '#/components/schemas/Model267' tradingPlan: $ref: '#/components/schemas/Model268' accounts: $ref: '#/components/schemas/Model270' createdAt: type: string updatedAt: type: string Model267: type: object description: Custom metadata Model268: type: object properties: id: type: string name: type: string description: type: string price: type: number currency: type: string durationDays: type: number accountSize: type: number Model270: type: array items: $ref: '#/components/schemas/Model269' Model269: type: object properties: id: type: string accountNumber: type: string status: type: string initialBalance: type: number currentBalance: type: number startedAt: type: string completedAt: type: string userId: type: string userEmail: 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 purchases for your organization](/platform-api/purchases/get-purchases-for-your-organization.md) - [Get a specific trader](/platform-api/traders/get-a-specific-trader.md) - [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 trading plan](/platform-api/trading-plans/get-a-specific-trading-plan.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.