> ## 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 signed upload URLs for ticket attachments > Attachments are uploaded directly to storage, not through this API. Send the file names, types, and sizes; you get back one signed upload target per file (valid ~2 hours, single use). PUT each file's bytes to its `signedUrl` (header `Content-Type: `), then reference the returned `path` in the ticket or comment you create. Screenshots (PNG/JPG/WebP/GIF) and recordings (MP4/MOV/WebM) up to 50 MB, max 5 per request. ## Example ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/support/uploads" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{"files": [{"name": "screenshot.png", "contentType": "image/png", "size": 482133}]}' ``` **Authentication:** send your organization API key in the `X-API-Key` header. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/organization/support/uploads 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/uploads: post: tags: - Support summary: Get signed upload URLs for ticket attachments description: >- Attachments are uploaded directly to storage, not through this API. Send the file names, types, and sizes; you get back one signed upload target per file (valid ~2 hours, single use). PUT each file's bytes to its `signedUrl` (header `Content-Type: `), then reference the returned `path` in the ticket or comment you create. Screenshots (PNG/JPG/WebP/GIF) and recordings (MP4/MOV/WebM) up to 50 MB, max 5 per request. ## Example ```bash curl -X POST "https://api.hyperprop.com/platform/v1/organization/support/uploads" \ -H "X-API-Key: hp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{"files": [{"name": "screenshot.png", "contentType": "image/png", "size": 482133}]}' ``` **Authentication:** send your organization API key in the `X-API-Key` header. operationId: postV1OrganizationSupportUploads requestBody: content: application/json: schema: $ref: '#/components/schemas/Model662' responses: '200': description: Success — one upload target per file content: '*/*': schema: $ref: '#/components/schemas/Model665' '400': description: Validation error '401': description: Unauthorized content: '*/*': schema: $ref: '#/components/schemas/Model311' '500': description: Internal error content: '*/*': schema: $ref: '#/components/schemas/Model312' security: - X-API-Key: [] components: schemas: Model662: type: object properties: files: $ref: '#/components/schemas/files' required: - files Model665: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model664' 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 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 files: type: array minItems: 1 maxItems: 5 items: $ref: '#/components/schemas/Model661' Model664: type: object properties: uploads: $ref: '#/components/schemas/uploads' Model661: type: object properties: name: type: string example: screenshot.png minLength: 1 maxLength: 255 contentType: $ref: '#/components/schemas/Model660' size: type: integer example: 482133 minimum: 1 maximum: 52428800 required: - name - contentType - size uploads: type: array items: $ref: '#/components/schemas/Model663' Model660: type: string example: image/png enum: - image/png - image/jpeg - image/webp - image/gif - video/mp4 - video/quicktime - video/webm Model663: type: object properties: path: type: string description: Reference this path in the ticket/comment attachments example: a6fcc0ce-…/1f2e…/screenshot.png token: type: string description: Upload token, for clients that send it separately from the URL signedUrl: type: string description: PUT the file bytes here name: type: string example: screenshot.png 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 support ticket with its reply thread](/platform-api/support/get-a-support-ticket-with-its-reply-thread.md) - [Create a support ticket](/platform-api/support/create-a-support-ticket.md) - [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) - [Upload organization logo](/platform-api/organization-profile/upload-organization-logo.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.