# Get signature structure

Get the signature structure affixed to the uploaded document (**CAdES only**) as a JSON report.
The returned object includes:
* `code`: HTTP status as string (e.g. `"200 OK"`)
* `result.report`: the signature structure
* `result.errors`: list of errors (empty array when none)

See the schemas section for a practical, navigable structure (kept permissive because the report can be large and varies by signature).

Endpoint: GET /documents/{document-id}/report
Version: 1.0
Security: AuthToken

## Security:

  - `AuthToken` (unknown)
    apiKey in header Authorization

## Path parameters:

  - `document-id` (string, required)
    Unique document identifier returned by upload (hexadecimal)

## Response 200:

  - `200` (unknown)
    Signature structure report

## Response 200 fields (application/json):

  - `code` (string, required)
    Example: 200 OK

  - `result` (object, required)

  - `result.report` (object, required)
    Signature structure for CAdES signatures (CMS SignedData-oriented).
The exact structure can be large and depends on the signature contents; the schema is permissive but documents key parts.

  - `result.report.content_type` (string)
    OID of the content (e.g. SignedData OID)
    Example: 1.2.840.113549.1.7.2

  - `result.report.content_name` (string)
    Common name associated with the OID
    Example: signedData

  - `result.report.content` (object)

  - `result.errors` (array, required)

  - `result.errors.where` (string)
    JSON path / identifier of where the error occurred

  - `result.errors.what` (string)
    Error identifier key (can be mapped via `messages` in verification report)

## Response 401:

  - `401` (unknown)
    Unauthorized (invalid or missing token)

## Response 401 fields (application/json):

  - `title` (string)

  - `description` (string)

  - `code` (string)

  - `message` (string)

## Response 404:

  - `404` (unknown)
    Resource not found (document expired/missing or wrong id)

## Response 404 fields (application/json):

  - `code` (string, required)
    Example: 404 Not Found

  - `description` (string)

## Response 502:

  - `502` (unknown)
    Upstream/service error (HTML body)

## Response 401 examples:

  - `invalidToken` (unknown)

## Response 404 examples:

  - `notFound` (unknown)

