> ## 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.

# マニフェスト検証

> 書き込みなしでマニフェストを完全検証。問題一覧とプレビューカード。

**`POST`** `https://api-datahub.octoparse.com/v1/data-apps/validate`

Authentication: API key required (`Authorization: Bearer <API Key>`).

Stage one of two-phase publish: full validation of structure, cross-block rules, self-publish guardrails, code-package checks, and filename checks — the same rules used at publish time. Returns the issue list and a preview card. This endpoint is the sole authority on pass/fail; do not second-guess from field tables in the docs.

## Request

### Request body

<ParamField body="manifest" type="string" required>
  Manifest source text as a YAML or JSON string.
</ParamField>

<ParamField body="files" type="object">
  Attached files. Keys are relative paths; values are text (used for code-kind or when a README is present).
</ParamField>

<ParamField body="secrets" type="object">
  Map of secret name to plaintext. The validate endpoint does not store them.
</ParamField>

### Example request

```bash theme={null}
curl -X POST \
  -H "Authorization: Bearer $OCTOPARSE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"manifest": "spec_version: \"0.2\"\nidentity:\n  app_name: reviews-query\n  name: Product review lookup\n  …"}' \
  "https://api-datahub.octoparse.com/v1/data-apps/validate"
```

## Response

### 200 success

```json theme={null}
{
  "data": {
    "valid": false,
    "errors": [
      {
        "path": "$",
        "message": "'identity' is a required property"
      },
      {
        "path": "$",
        "message": "'input' is a required property"
      },
      "…"
    ],
    "card": null
  }
}
```

The payload is wrapped in `data`. Fields:

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

<ResponseField name="errors" type="object[]">
  Issue list. Each item has `path` (JSON path) and `message`.

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

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

<ResponseField name="card" type="object">
  Preview card when valid; `null` when invalid.
</ResponseField>

### Errors

| HTTP | `code`         | `category`  | Description                 |
| ---- | -------------- | ----------- | --------------------------- |
| 401  | `unauthorized` | `forbidden` | Missing or invalid API key. |

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

## Client libraries

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