POSTpartial

Report a defect against the exact displayed derivative

Controlled by PEOPLES_COURT_API_CANONICAL_ROUTES. The shared operation rechecks current authority and pinned Rules. Partner reports require defects:report and bind the exact derivative shown to the reporting party. Resolution stays internal.

/api/cases/{id}/evidence-processing/{sourceId}/defectsreportProcessingDefectPreview

Authentication and authority

Use one listed account-session, scoped OAuth, or partner credential alternative. Account tokens retain the approving account’s authority. Cookie-authenticated writes require same-origin authorization. Alternatives are OR; schemes in one alternative are AND.

CanonicalSession

CanonicalPartnerBearer

AccountOAuth

Account tokens authorize only their approving account and case scope. S256 PKCE is mandatory on the code flow. Explicit reacceptance is required after Rules/disclosure changes.

Parameters

NameLocationRequirementSchema
idpathRequired{"type":"string"}
sourceIdpathRequired{"type":"string"}
Idempotency-Key

Reuse across compatibility and canonical aliases to recover the same committed act. Changed typed input conflicts.

headerOptional{"type":"string"}

Request body

Required request body.

application/json

{
  "$ref": "#/components/schemas/ProcessingDefectPreview",
  "type": "object",
  "required": [
    "jobId",
    "derivativeId",
    "manifestId",
    "text"
  ],
  "properties": {
    "jobId": {
      "type": "string"
    },
    "derivativeId": {
      "type": "string"
    },
    "manifestId": {
      "type": "string"
    },
    "text": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000
    }
  }
}

Responses

201

Authorized operation result.

application/json

{
  "$ref": "#/components/schemas/CanonicalReportProcessingDefectPreviewResponse",
  "type": "object",
  "properties": {
    "data": {
      "$ref": "#/components/schemas/CanonicalProcessingDefectResult",
      "type": "object",
      "properties": {
        "id": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "const": "open"
        }
      },
      "required": [
        "id",
        "status"
      ]
    },
    "requestId": {
      "type": "string"
    }
  },
  "required": [
    "data",
    "requestId"
  ],
  "x-code-source": "lib/proceeding/evidence-processing.ts"
}
404

Preview disabled or authorized resource unavailable.

default

RFC 9457 style problem response.

application/problem+json

{
  "$ref": "#/components/schemas/Problem",
  "type": "object",
  "required": [
    "type",
    "title",
    "status",
    "code",
    "detail",
    "requestId"
  ],
  "properties": {
    "type": {
      "type": "string",
      "format": "uri"
    },
    "title": {
      "type": "string"
    },
    "status": {
      "type": "integer"
    },
    "code": {
      "type": "string"
    },
    "detail": {
      "type": "string"
    },
    "requestId": {
      "type": "string"
    }
  }
}

Example response

Successful response

{
  "data": {
    "id": "id_test",
    "status": "open"
  },
  "requestId": "requestId_test"
}

Errors

Read the response status and stable error code. See errors and rate limits for recovery. Refresh the resource before resolving a state or digest conflict.

Idempotency and retries

  • For throttling, honor Retry-After when present. Back off on retryable server failures.
  • Send a unique Idempotency-Key. An exact retry returns the stored result; reusing the key with a different request fails.
  • The request is accepted only when its credential, authority, case state, and resource preconditions are satisfied.