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

# Get a saved LoRA Style

Get a saved LoRA Style with the FLORA API: GET /loras/{styleId}.

Reads saved Style readiness, compatible base-model family and prompt metadata in an explicitly authorized workspace. Missing, deleted and inaccessible Styles return 404. A failed training run may remove its pending Style; inspect the run\_id returned by training for the failure and final charge. Weight download URLs and training images are not exposed.

```http
GET https://app.flora.ai/api/v1/loras/{styleId}
```

* **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.loras.retrieve()`.
* **Operation ID:** `getLora`.

## Example

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

```bash
curl -X GET 'https://app.flora.ai/api/v1/loras/sty_abc123?workspace_id=ws_abc123' \
  -H "Authorization: Bearer $FLORA_API_KEY"
```

{% endtab %}

{% tab title="TypeScript SDK" %}

```typescript
import { FloraClient } from '@flora-ai/flora';

const client = new FloraClient({ apiKey: process.env['FLORA_API_KEY'] });

const lora = await client.loras.retrieve({
  styleId: 'sty_abc123',
  workspace_id: 'ws_abc123',
});
console.log(lora);
```

{% endtab %}
{% endtabs %}

## Path parameters

| Name      | Type   | Required | Description                                                                                    |
| --------- | ------ | -------- | ---------------------------------------------------------------------------------------------- |
| `styleId` | string | Yes      | Saved Style identifier returned by LoRA training. Pattern: `^sty_\S+$`. Example: `sty_abc123`. |

## Query parameters

| Name           | Type   | Required | Description                                                                           |
| -------------- | ------ | -------- | ------------------------------------------------------------------------------------- |
| `workspace_id` | string | Yes      | Workspace in which the Style will be used. Pattern: `^ws_\S+$`. Example: `ws_abc123`. |

## Responses

### 200: Saved Style returned.

| Field          | Type           | Required | Description                                                                                                                |
| -------------- | -------------- | -------- | -------------------------------------------------------------------------------------------------------------------------- |
| `style_id`     | string         | Yes      | Saved Style identifier. Pattern: `^sty_\S+$`. Example: `sty_abc123`.                                                       |
| `name`         | string         | Yes      | Saved Style name                                                                                                           |
| `base_model`   | string or null | Yes      | Compatible LoRA base-model family, when recorded                                                                           |
| `status`       | string         | Yes      | Ready means the saved Style has usable weights or a provider Style identifier. One of: `training`, `ready`, `unavailable`. |
| `keyword`      | string or null | Yes      | Saved trigger keyword applied by compatible generation models                                                              |
| `style_prompt` | string or null | Yes      | Saved model-specific prompt convention, when available                                                                     |
| `run_id`       | string or null | Yes      | Original training run, when the Style was trained in Flora. Pattern: `^run_\S+$`. Example: `run_abc123`.                   |

## 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/loras/getlora.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.
