> ## 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 support ticket with its reply thread > One ticket in full: description, the reply thread (your team's comments and Hyperprop's replies, oldest first), and attachments with time-limited download URLs (valid 1 hour — re-fetch the ticket for fresh links). ## Example ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/support/tickets/e4b1a2c3-d4e5-4f60-8192-a3b4c5d6e7f8" \ -H "X-API-Key: hp_live_your_key_here" ``` **Authentication:** send your organization API key in the `X-API-Key` header. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/support/tickets/{ticketId} 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/support/tickets/{ticketId}: get: tags: - Support summary: Get a support ticket with its reply thread description: >- One ticket in full: description, the reply thread (your team's comments and Hyperprop's replies, oldest first), and attachments with time-limited download URLs (valid 1 hour — re-fetch the ticket for fresh links). ## Example ```bash curl -X GET "https://api.hyperprop.com/platform/v1/organization/support/tickets/e4b1a2c3-d4e5-4f60-8192-a3b4c5d6e7f8" \ -H "X-API-Key: hp_live_your_key_here" ``` **Authentication:** send your organization API key in the `X-API-Key` header. operationId: getV1OrganizationSupportTicketsTicketid parameters: - x-format: guid: true name: ticketId in: path required: true schema: type: string responses: '200': description: Success — the full ticket content: '*/*': schema: $ref: '#/components/schemas/Model413' '401': description: Unauthorized content: '*/*': schema: $ref: '#/components/schemas/Model311' '404': description: Ticket not found content: '*/*': schema: $ref: '#/components/schemas/Model414' '500': description: Internal error content: '*/*': schema: $ref: '#/components/schemas/Model312' security: - X-API-Key: [] components: schemas: Model413: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model412' Model311: type: object properties: statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Invalid or expired token code: type: string example: UNAUTHORIZED Model414: type: object properties: statusCode: type: number example: 404 error: type: string example: Not Found message: type: string example: Ticket not found code: type: string example: NOT_FOUND Model312: type: object properties: statusCode: type: number example: 500 error: type: string example: Internal Server Error message: type: string example: Failed to load tickets code: type: string example: SUPPORT_ERROR Model412: type: object properties: ticket: $ref: '#/components/schemas/Model308' Model308: type: object properties: id: type: string example: e4b1a2c3-d4e5-4f60-8192-a3b4c5d6e7f8 x-format: guid: true ticketNumber: type: integer description: Human-friendly sequential reference (#42) example: 42 organizationId: type: string example: a6fcc0ce-eb28-4f43-b256-96a3144b0d34 x-format: guid: true createdByUserId: type: string example: 0b1c2d3e-4f50-6172-8394-a5b6c7d8e9f0 createdByEmail: type: string example: ops@yourfirm.com createdByName: type: string example: Your Firm LLC type: $ref: '#/components/schemas/type' title: type: string example: Fills missing on ES orders since this morning description: type: string example: Orders 123/456 filled on the exchange but no fills showed… accountIds: $ref: '#/components/schemas/accountIds' occurredAt: type: string description: When the issue happened (UTC; shown in Eastern Time in the portal) example: '2026-08-27T13:45:00.000Z' x-format: isoDate: true priority: $ref: '#/components/schemas/priority' status: $ref: '#/components/schemas/Model305' attachments: $ref: '#/components/schemas/attachments' comments: $ref: '#/components/schemas/comments' commentCount: type: integer example: 2 createdAt: type: string x-format: isoDate: true updatedAt: type: string x-format: isoDate: true type: type: string example: incident enum: - incident - feature_request accountIds: type: array description: Trading account ids the report concerns example: - 1e7c9f02-e980-4410-b81f-39599bb6fa47 items: type: string priority: type: string example: high enum: - low - normal - high - urgent Model305: type: string description: >- open — filed and queued; investigating — our team is on it; resolved — done (fixed, shipped, or declined with a reply) example: open enum: - open - investigating - resolved attachments: type: array items: $ref: '#/components/schemas/Model306' comments: type: array description: >- Reply thread, oldest first. Empty in list responses — fetch the ticket for the full thread. items: $ref: '#/components/schemas/Model307' Model306: type: object properties: path: type: string description: >- Storage path returned by the uploads endpoint. Must belong to your organization. example: a6fcc0ce-eb28-4f43-b256-96a3144b0d34/1f2e.../screenshot.webp maxLength: 500 name: type: string example: screenshot.webp minLength: 1 maxLength: 255 size: type: integer example: 482133 minimum: 1 maximum: 52428800 contentType: $ref: '#/components/schemas/contentType' signedUrl: type: string description: >- Time-limited download URL (1 hour). Present on ticket detail responses. required: - path - name - size - contentType Model307: type: object properties: id: type: string example: 7d5c2f4e-9a1b-4c3d-8e2f-6a5b4c3d2e1f x-format: guid: true authorType: $ref: '#/components/schemas/authorType' authorId: type: string authorName: type: string example: ops@yourfirm.com body: type: string example: We shipped a fix — can you confirm it looks right now? attachments: $ref: '#/components/schemas/attachments' createdAt: type: string example: '2026-08-27T16:21:00.000Z' x-format: isoDate: true contentType: type: string example: image/webp enum: - image/png - image/jpeg - image/webp - image/gif - video/mp4 - video/quicktime - video/webm authorType: type: string description: >- "firm" — written by your team; "hyperprop" — a reply from Hyperprop support example: hyperprop enum: - firm - hyperprop 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 - [Reply on a support ticket](/platform-api/support/reply-on-a-support-ticket.md) - [List your support tickets](/platform-api/support/list-your-support-tickets.md) - [Create a support ticket](/platform-api/support/create-a-support-ticket.md) - [Get signed upload URLs for ticket attachments](/platform-api/support/get-signed-upload-urls-for-ticket-attachments.md) - [Introduction](/introduction.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.