> ## Documentation Index > Fetch the complete documentation index at: https://docs.moda.app/llms.txt > Use this file to discover all available pages before exploring further. # Register Upload > Finalize a signed-URL upload into a Moda file row. Streams the staged blob through ``download_with_hash`` (writes to a temp file on disk, hashes in 8 KiB chunks) so a 250 MB upload never fully materializes in process memory — loading even a couple of those concurrently on Cloud Run would risk OOM and defeat the point of the direct-to-storage flow. Deduplicates against existing team files by content hash. On a dedup miss the staged blob is server-side-copied to the canonical ``teams//files/`` key via ``storage.copy`` (zero data transfer on GCS) and registered via ``create_file_from_storage``. The pending blob is best-effort deleted either way. ## OpenAPI ````yaml /openapi/moda-public-api.yaml post /uploads/register openapi: 3.1.0 info: title: Moda Public API description: > Programmatic access to Moda's canvas design platform. Create designs, export assets, manage brand kits, and run AI design tasks. ## Versioning Pin response shapes with a calendar-dated `Moda-Version` header (e.g. `2026-05-01`). **The pin is global** — it applies to every endpoint in the request, not just the one you adopted it for, so raising it to use a new endpoint also moves your other responses to that version's shapes. ### Migrating `2026-04-12` → `2026-05-01` - **Tasks** move from the flat `JobResponse` (`job_id`, `canvas_url`, `can_export`) to the canonical `Task` envelope. The export artifact is now under `result.export` as `{url, format, page_count}`; update any code that read the export URL from the old top-level fields. - **Multi-page PNG/JPEG exports are delivered as a single `.zip`** of per-page files (`page-1.png`, …), so `result.export.format` is `zip`. For one bundled document instead, request `format=pdf` or `pptx`; for a single image, pass `page_number`. version: 1.0.0 x-moda-api-version: '2026-05-01' servers: - url: https://api.moda.app/v1 description: Production security: [] tags: - name: canvases description: List, search, read, export, and share canvases - name: tasks description: Start and monitor AI design tasks - name: organizations description: List organizations and teams - name: credits description: Check credit balance and usage - name: brand-kits description: Manage brand kits - name: remix description: Duplicate and edit canvases - name: share-links description: Resolve share URLs to canvas identifiers - name: uploads description: Upload files for use as attachments - name: usage description: Aggregate API usage stats for the caller's team - name: embed description: Signed iframe embed sessions - name: web description: 'Metered web research: search and page reading' - name: websites description: >- Create, update, publish, screenshot, and manage hosted multi-page static sites - name: drive description: >- Organize the workspace: folders, the folder tree, and item move/rename/visibility/delete for folders, canvases, and files paths: /uploads/register: post: tags: - uploads summary: Register Upload description: |- Finalize a signed-URL upload into a Moda file row. Streams the staged blob through ``download_with_hash`` (writes to a temp file on disk, hashes in 8 KiB chunks) so a 250 MB upload never fully materializes in process memory — loading even a couple of those concurrently on Cloud Run would risk OOM and defeat the point of the direct-to-storage flow. Deduplicates against existing team files by content hash. On a dedup miss the staged blob is server-side-copied to the canonical ``teams//files/`` key via ``storage.copy`` (zero data transfer on GCS) and registered via ``create_file_from_storage``. The pending blob is best-effort deleted either way. operationId: registerUpload parameters: - $ref: '#/components/parameters/ModaVersion' requestBody: content: application/json: schema: $ref: '#/components/schemas/RegisterUploadRequest' required: true responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/FileUploadResponse' '401': description: Authentication required. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '403': description: Permission denied for this scope. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '404': description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '409': description: Conflict (idempotency / resource state). content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '422': description: Request validation failed. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' '500': description: Internal error. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' security: - API Key: [] components: parameters: ModaVersion: name: Moda-Version in: header required: false description: >- Calendar-dated API version pin. New integrations should pin `2026-05-01` to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: `2026-04-12`); that default advances on each [sunset date](/api-reference/versioning). Any unsupported value returns 400 `unsupported_version`. example: '2026-05-01' schema: type: string enum: - '2026-04-12' - '2026-05-01' default: '2026-05-01' example: '2026-05-01' schemas: RegisterUploadRequest: properties: storage_key: type: string title: Storage Key description: >- ``storage_key`` returned by a prior ``POST /v1/uploads/url`` after the PUT completed. filename: anyOf: - type: string maxLength: 512 - type: 'null' title: Filename description: >- Filename to record on the File row. Defaults to the basename embedded in ``storage_key``. mime_type: anyOf: - type: string - type: 'null' title: Mime Type description: >- MIME type to record on the File row. Defaults to the type the signed URL was originally bound to (inferred from the filename when not supplied). folder_id: anyOf: - type: string pattern: ^fld_[0-9A-HJKMNP-TV-Za-hjkmnp-tv-z]{26}$ description: >- Prefixed ``fld_`` wire ID (Crockford base32 body) — the canonical, recommended form. For back-compat, **a bare UUID string is also accepted** in both path parameters and JSON request bodies (older integrations that stored raw UUIDs keep working). Both are permanent, supported inputs. example: fld_01HT9WK8N3M2J4A5Z6P7Q8R9TV - type: 'null' title: Folder Id description: >- Destination drive folder (``fld_...`` or a bare folder UUID). The file adopts the folder's visibility, exactly like an in-app upload into that folder. An unknown or inaccessible folder is a 404 ``folder_not_found``; a folder you can see but not edit, or a read-only namespace (Skills, Brand Kits), is a 403 ``folder_write_denied``; brand-kit-managed folders are a 403 ``brand_kit_folder_protected``. Omit to land unfiled (library root). additionalProperties: false type: object required: - storage_key title: RegisterUploadRequest FileUploadResponse: properties: id: type: string pattern: ^file_[0-9A-HJKMNP-TV-Za-hjkmnp-tv-z]{26}$ title: Id description: Unique file identifier (prefixed ``file_...``). example: file_01HT9WK8N3M2J4A5Z6P7Q8R9TV url: type: string title: Url description: Stable proxy URL for the uploaded file. Use this in attachment URLs. filename: type: string title: Filename description: Filename of the uploaded file. mime_type: type: string title: Mime Type description: MIME type of the file. size_bytes: anyOf: - type: integer - type: 'null' title: Size Bytes description: File size in bytes. was_duplicate: type: boolean title: Was Duplicate description: True if an identical file already existed (deduplicated). default: false folder_id: anyOf: - type: string pattern: ^fld_[0-9A-HJKMNP-TV-Za-hjkmnp-tv-z]{26}$ description: >- Prefixed ``fld_`` wire ID (Crockford base32 body) — the canonical, recommended form. For back-compat, **a bare UUID string is also accepted** in both path parameters and JSON request bodies (older integrations that stored raw UUIDs keep working). Both are permanent, supported inputs. example: fld_01HT9WK8N3M2J4A5Z6P7Q8R9TV - type: 'null' title: Folder Id description: >- Drive folder the file landed in (``fld_...``), or ``null`` for the unfiled library root. type: object required: - id - url - filename - mime_type title: FileUploadResponse ErrorEnvelope: properties: type: $ref: '#/components/schemas/ErrorType' code: type: string title: Code description: >- Stable machine string keyed to doc_url. Never changes once published. message: type: string title: Message description: >- Human-readable message, for developers. Not localized, not user-facing. doc_url: type: string title: Doc Url description: Permalink to the docs page for this code. request_id: anyOf: - type: string - type: 'null' title: Request Id description: Correlator for logs/Sentry/audit. causes: anyOf: - items: $ref: '#/components/schemas/ErrorEnvelope' type: array - type: 'null' title: Causes description: Aggregated upstream failures (e.g. per-page export errors). details: anyOf: - additionalProperties: true type: object - type: 'null' title: Details description: >- Code-specific detail payload (e.g. validation field list). Callers should pass ``None`` rather than ``{}`` to omit the key from the response. retry_after_ms: anyOf: - type: integer - type: 'null' title: Retry After Ms description: Hint for rate-limited or transient errors. retryable: anyOf: - type: boolean - type: 'null' title: Retryable description: >- Explicit retryability for this code, from the error-code registry: ``false`` means retrying the same request cannot succeed (fix the input / resource first); ``true`` means the condition is transient and a retry (with backoff / after the blocker clears) can succeed. Omitted for codes whose retryability is context-dependent — do not derive it from ``type`` or the HTTP status when this field is present. type: object required: - type - code - message - doc_url title: ErrorEnvelope description: >- Canonical error payload, nested under the top-level ``{"error": ...}`` key. ErrorType: type: string enum: - invalid_request - authentication - permission - not_found - conflict - rate_limited - idempotency_conflict - unprocessable - upstream_error - internal_error title: ErrorType description: Closed set of high-level categories SDKs branch on. securitySchemes: API Key: type: http description: API key from Settings > Developer > REST API scheme: bearer ````