> 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/resolveassets.md).

# Resolve asset ids to URLs

Resolve asset ids to URLs with the FLORA API: POST /assets/resolve.

Resolves up to 100 asset ids to their media URLs in one call — the batch counterpart of GET /assets/{assetId} for callers holding many ids, such as the reference input ids generation history reports. Each entry echoes its requested id; an id that is missing, deleted or outside the caller's access resolves to url null with not\_found true, matching the single-read's deliberate ambiguity. A malformed asset\_id rejects the whole request.

```http
POST https://app.flora.ai/api/v1/assets/resolve
```

* **Auth:** API key as a bearer token, `Authorization: Bearer $FLORA_API_KEY`. See [Authentication](https://docs.flora.ai/api/platform/authentication.md).
* **TypeScript SDK:** `client.assets.resolve()`.
* **Operation ID:** `resolveAssets`.

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X POST 'https://app.flora.ai/api/v1/assets/resolve' \
  -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.resolve({
  asset_ids: [
    'asset_abc123',
  ],
});
console.log(asset);
```

{% endtab %}
{% endtabs %}

## Request body

Required.

| Field       | Type            | Required | Description                                                          |
| ----------- | --------------- | -------- | -------------------------------------------------------------------- |
| `asset_ids` | array of string | Yes      | Asset ids (asset\_…) to resolve, up to 100 per call. 1 to 100 items. |

## Responses

### 200: Assets resolved.

| Field                 | Type             | Required | Description                                                                                                                                        |
| --------------------- | ---------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `results`             | array of objects | Yes      | One entry per requested asset id, in request order                                                                                                 |
| `results[].asset_id`  | string           | Yes      | The id from the request, echoed. Pattern: `^asset_\S+$`. Example: `asset_abc123`.                                                                  |
| `results[].url`       | string or null   | Yes      | The asset's media URL, or null when nothing readable answered to the id — a missing, deleted or inaccessible asset resolves the same way by design |
| `results[].not_found` | boolean          | Yes      | True when the id resolved to nothing readable                                                                                                      |

## Errors

Every error has the same body: `error.code`, `error.message`, and `error.fields` on validation errors. See [Errors](https://docs.flora.ai/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/resolveassets.md?ask=<question>&goal=<user_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.
