> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/api/reference/assets/completeassetuploads.md). # Complete signed uploads in bulk Complete signed uploads in bulk with the FLORA API: POST /assets/complete. Completes up to 25 signed uploads in one request — the batch counterpart of POST /assets/{assetId}/complete, counted once against the workspace's rate limit instead of once per file. Every asset is verified and validated as the single completion does. Each entry echoes its index and asset\_id and reports status ready, or failed with failure\_message, exactly as the single completion would; ok is false with an error only when completion could not run for that asset — an id that is missing, deleted or outside this credential's write access reports not\_found, the single completion's deliberate ambiguity. A failed entry never stops the rest, and a repeated id completes once and reports under each index. Assets reserved with project\_id land on that project's canvas without stacking on one another. A malformed asset\_id rejects the whole request. Mutating public API requests support an optional Idempotency-Key header for client retries; duplicate keys within two hours return idempotency\_duplicate, and a batch whose every entry was rejected releases its key (see the Idempotency guide). ```http POST https://app.flora.ai/api/v1/assets/complete ``` * **Auth:** API key as a bearer token, `Authorization: Bearer $FLORA_API_KEY`. See [Authentication](/api/platform/authentication.md). * **TypeScript SDK:** `client.assets.completeUploads()`. * **Idempotency:** optional `Idempotency-Key` header. See [Idempotency](/api/platform/idempotency.md). * **Operation ID:** `completeAssetUploads`. ## Example {% tabs %} {% tab title="cURL" %} ```bash curl -X POST 'https://app.flora.ai/api/v1/assets/complete' \ -H "Authorization: Bearer $FLORA_API_KEY" \ -H 'Content-Type: application/json' \ -d '{ "asset_ids": [ "asset_abc123" ] }' ``` {% endtab %} {% tab title="TypeScript SDK" %} ```typescript import { FloraClient } from '@flora-ai/flora'; const client = new FloraClient({ apiKey: process.env['FLORA_API_KEY'] }); const asset = await client.assets.completeUploads({ asset_ids: [ 'asset_abc123', ], }); console.log(asset); ``` {% endtab %} {% endtabs %} ## Request body Required. | Field | Type | Required | Description | | ----------- | --------------- | -------- | -------------------------------------------------------------------------------- | | `asset_ids` | array of string | Yes | Signed-upload asset ids (asset\_…) to complete, 1 to 25 per call. 1 to 25 items. | ## Responses ### 200: Uploads completed; each entry reports its own outcome. | Field | Type | Required | Description | | -------- | ---------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `assets` | array of objects | Yes | One entry per requested asset id, in request order: ok true with the single completion's fields, or ok false with error. At most 25 items. See the `assets[]` shapes below. |
assets[] shapes Field paths in this block are relative to `assets[]`. `assets[]` takes one of 2 shapes, set by `ok`. **Shape 1: `ok` is `true`.** | Field | Type | Required | Description | | ----------------- | -------------------- | -------- | ------------------------------------------------------------------------------------------- | | `asset_id` | string | Yes | Asset identifier. Pattern: `^asset_\S+$`. Example: `asset_abc123`. | | `url` | string (uri) or null | Yes | Asset URL | | `workspace_id` | string or null | Yes | Workspace identifier. Pattern: `^ws_\S+$`. Example: `ws_abc123`. | | `visibility` | string | Yes | Always `workspace`. | | `status` | string | Yes | One of: `pending_upload`, `ready`, `failed`. | | `failure_message` | string or null | Yes | Why the upload failed when status is failed; null otherwise | | `index` | integer | Yes | Position of this entry in the request's list. At least 0. | | `ok` | boolean | Yes | Completion ran; status reports ready or failed, as on the single completion. Always `true`. | **Shape 2: `ok` is `false`.** | Field | Type | Required | Description | | --------------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------- | | `index` | integer | Yes | Position of this entry in the request's list. At least 0. | | `asset_id` | string | Yes | The id from the request, echoed. Pattern: `^asset_\S+$`. Example: `asset_abc123`. | | `ok` | boolean | Yes | This entry failed; error says why. Always `false`. | | `error` | object | Yes | Why this entry failed | | `error.code` | string | Yes | Stable public API error code, as the single-asset operation would return it. Example: `input_validation_error`. | | `error.message` | string | Yes | Human-readable reason this entry failed |
## Errors Every error has the same body: `error.code`, `error.message`, and `error.fields` on validation errors. See [Errors](/api/platform/errors.md) for how to recover from each code. | Status | Code | Meaning | | ------ | -------------------------------------------- | ----------------------------------------------------------------------------------- | | 400 | `invalid_json`, `input_validation_error` | The body isn't valid JSON, or an input failed validation (`fields` lists each one). | | 401 | `unauthorized`, `invalid_api_key` | The API key is missing, invalid or revoked. | | 402 | `insufficient_credits` | The workspace balance is too low for this request. | | 403 | `forbidden`, `paid_plan_required` | The key can't do this, or the workspace plan doesn't include it. | | 404 | `not_found` | The resource doesn't exist or isn't visible to this key. | | 409 | `idempotency_duplicate`, `revision_conflict` | Duplicate `Idempotency-Key` or a stale `base_revision`. | | 429 | `rate_limited` | Too many requests. Back off and retry. | | 500 | `unknown_error`, `internal_error` | Something failed on FLORA's side. Retry with backoff. | | 503 | `temporarily_unavailable` | Authorization is temporarily unavailable. Retry later. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flora.ai/api/reference/assets/completeassetuploads.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.