> ## 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:** Accepts either `Authorization: Bearer ` (dashboard) or `X-API-Key: hp_live_...` (programmatic). ## 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: Authentication description: >- User authentication - signup, signin, signout, password reset, email verification, OAuth, and MFA - name: User description: >- User account management - profile, notifications, agreements, dismissals, and audit logs. Requires Bearer token. - name: Organization description: >- Organization management - profile, team, trading accounts, plans, and rules. Supports **dual authentication**: Bearer JWT token (dashboard users) OR X-API-Key (programmatic access). - name: Demo description: >- Demo account management - import, list, and delete demo trading accounts. Requires Bearer token. - name: Market Data description: CME futures contracts and market data. Requires Bearer token. - name: System description: System endpoints - health checks and connectivity paths: /v1/organization/support/uploads: post: tags: - Organization 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:** Accepts either `Authorization: Bearer ` (dashboard) or `X-API-Key: hp_live_...` (programmatic). operationId: postV1OrganizationSupportUploads requestBody: content: application/json: schema: $ref: '#/components/schemas/Model613' responses: '200': description: Success — one upload target per file content: '*/*': schema: $ref: '#/components/schemas/Model616' '400': description: Validation error '401': description: Unauthorized content: '*/*': schema: $ref: '#/components/schemas/Model294' '500': description: Internal error content: '*/*': schema: $ref: '#/components/schemas/Model295' security: - Bearer: [] - X-API-Key: [] components: schemas: Model613: type: object properties: files: $ref: '#/components/schemas/files' required: - files Model616: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model615' Model294: 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 Model295: 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/Model612' Model615: type: object properties: uploads: $ref: '#/components/schemas/uploads' Model612: type: object properties: name: type: string example: screenshot.png minLength: 1 maxLength: 255 contentType: $ref: '#/components/schemas/Model611' size: type: integer example: 482133 minimum: 1 maximum: 52428800 required: - name - contentType - size uploads: type: array items: $ref: '#/components/schemas/Model614' Model611: type: string example: image/png enum: - image/png - image/jpeg - image/webp - image/gif - video/mp4 - video/quicktime - video/webm Model614: 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 Supabase-style clients) signedUrl: type: string description: PUT the file bytes here name: type: string example: screenshot.png securitySchemes: Bearer: type: apiKey name: Authorization in: header description: >- JWT Bearer token for user session auth. Format: "Bearer {token}". Used by User and Organization endpoints. X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key for programmatic access. Format: "hp_live_{key}". Used by Organization endpoints as an alternative to Bearer token. Keys are managed in the dashboard. ```` ## Related topics - [Get a support ticket with its reply thread](/platform-api/organization/get-a-support-ticket-with-its-reply-thread.md) - [Create a support ticket](/platform-api/organization/create-a-support-ticket.md) - [Reply on a support ticket](/platform-api/organization/reply-on-a-support-ticket.md) - [List your support tickets](/platform-api/organization/list-your-support-tickets.md) - [Upload community image](/platform-api/community/upload-community-image.md)