> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get workspace

> Read back the draft's raw text, files, revision, and validation result for continue-editing refill.

**`GET`** `https://api-datahub.octoparse.com/v1/data-apps/{app_id}/workspace`

Authentication: API key required (`Authorization: Bearer <API Key>`). App author only; others get `404`.

Raw manifest, attached files, revision, and current validation result — the refill source for "continue editing" in clients.

No draft returns `404 workspace-not-found`. That is a normal main-path state (new app, or published with no in-progress edits), not a fault. Clients should handle it explicitly instead of treating it as a server error.

## Request

### Path parameters

<ParamField path="app_id" type="string" required>
  App reference.
</ParamField>

### Example request

```bash theme={null}
curl \
  -H "Authorization: Bearer $OCTOPARSE_API_KEY" \
  "https://api-datahub.octoparse.com/v1/data-apps/carol/reviews-query/workspace"
```

## Response

### 200 success

```json theme={null}
{
  "data": {
    "app_name": "probe-b",
    "app_id": "app_6dfe4e839ccf",
    "namespace": "carol",
    "manifest": "\nspec_version: \"0.2\"\nidentity:\n  app_name: probe-b\n  name: Runs list probe source\n  summary: Test app for runs list pagination and filters\n  type: data\n  version:…",
    "files": {},
    "revision": 1,
    "valid": true,
    "issues": [],
    "content_hash": "267d174fa14b05d66608cbd8315242f4b0f5b0b62a5fd94ffa852ee6cf62f978",
    "created_at": "2026-09-15T07:45:38.574191+00:00",
    "updated_at": "2026-09-15T07:45:38.574191+00:00"
  }
}
```

The payload is wrapped in `data`. Fields:

<ResponseField name="app_name" type="string" required>
  App name.
</ResponseField>

<ResponseField name="app_id" type="string" required>
  Stable app id.
</ResponseField>

<ResponseField name="namespace" type="string">
  Publisher username.
</ResponseField>

<ResponseField name="manifest" type="string" required>
  Raw manifest text.
</ResponseField>

<ResponseField name="files" type="object">
  Attached files.
</ResponseField>

<ResponseField name="revision" type="integer" required>
  Draft revision for `expected_revision` on save.
</ResponseField>

<ResponseField name="valid" type="boolean" required>
  Whether validation passed.
</ResponseField>

<ResponseField name="issues" type="object[]">
  Issue list.

  <Expandable title="fields">
    <ResponseField name="path" type="string" required>
      —
    </ResponseField>

    <ResponseField name="message" type="string" required>
      —
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="content_hash" type="string">
  Content hash; corresponds to a Build's `content_hash`.
</ResponseField>

<ResponseField name="created_at" type="string">
  Created time.
</ResponseField>

<ResponseField name="updated_at" type="string">
  Last saved time.
</ResponseField>

### Errors

| HTTP | `code`                | `category`  | Description                                                                       |
| ---- | --------------------- | ----------- | --------------------------------------------------------------------------------- |
| 401  | `unauthorized`        | `forbidden` | Missing or invalid API key.                                                       |
| 404  | `workspace-not-found` | `not_found` | This app has no in-progress draft. That is a normal main-path state, not a fault. |

Error responses use `{"error": {code, category, message, retryable}}`. See <a href="/docs/en/datahub/api/reference/introduction#errors">Errors</a>.

## Client libraries

The Python and JavaScript SDKs do not wrap this endpoint yet. Call REST directly.