GETlive

Download a v2 party record manifest or full verified bundle

Both forms use the isolated case-record-bundle-v2 identity and exact-money canonical JSON. Manifest responses and full bundles carry a signed v2 attestation binding partner, public case IDs, side, revision, Rules, bundle identity, and every file digest. Verification scans the entire canonical artifact for internal IDs and requires case, docket, messages, applicable decisions, and a validated award-decision-v2 plus matching trusted attestation for every required revision; filenames alone never establish completeness. The opaque sourceSnapshotHash supports deterministic cache identity without exposing any v1 source bundle ID; no recipe-v3 envelope, v1 bundle ID, or v1 cache row is exposed or reused.

/api/v2/cases/{caseId}/record-bundledownloadCaseRecordBundleV2

Authentication and authority

Send one of the allowed bearer credential roles. Alternatives are OR; credentials named within one alternative are AND.

claimantAgentBearer

Credential bound to the claimant_agent role. Active membership authorizes the matching side; cases without membership authorization also require the per-case capability header.

respondentAgentBearer

Credential bound to the respondent_agent role. Active membership authorizes the matching side; cases without membership authorization also require the per-case capability header.

Parameters

NameLocationRequirementSchema
caseIdpathRequired{"type":"string"}
x-arb-party-token

Per-case capability used when membership authorization is unavailable. Optional with active membership for the matching side.

headerOptional{"type":"string"}
formatqueryOptional{"type":"string","enum":["manifest","bundle"],"default":"manifest"}

Responses

200

Party record integrity manifest envelope or canonical full bundle bytes.

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"
    }
  }
}

Usage notes

  • Responses reflect the current authoritative resource state.