GETpartial

Poll committed, caller-scoped case events

Durable audit-derived event IDs and opaque cursors. Resume with after; default limit 50, maximum 100. Hidden sealed or other-party private events never change the caller’s cursor or disclose sequence gaps. Invalid, cross-case or undisclosed cursors return 422. The x-pc-compatibility: v1 docket snapshot is unchanged. Webhook caseEvent.id and caseEvent.cursor reconcile to this stream; delivery eventId and sequence retain their existing deduplication meaning.

/api/cases/{id}/eventsgetCaseEventsPreview

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.

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.

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"}
x-arb-party-token

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

headerOptional{"type":"string"}
x-pc-compatibility

Bounded compatibility inputs on the canonical URL. Existing scoped credentials retain v1 responses; role-bound credentials use grant-checked typed operations. Preserves each contract’s original journals, consent and disclosure. See /openapi/partner-v1.json for scoped credentials.

headerOptional{"type":"string","enum":["v1"]}
afterqueryOptional{"type":"string"}
limitqueryOptional{"type":"integer","minimum":1,"maximum":100,"default":50}

Responses

200

Caller-visible committed events

application/json

{
  "type": "object",
  "required": [
    "data",
    "requestId"
  ],
  "properties": {
    "data": {
      "$ref": "#/components/schemas/CanonicalCaseEventPage",
      "type": "object",
      "additionalProperties": false,
      "required": [
        "schemaVersion",
        "caseId",
        "events",
        "nextCursor",
        "hasMore"
      ],
      "properties": {
        "schemaVersion": {
          "type": "string",
          "const": "case-event-page-v1"
        },
        "caseId": {
          "type": "string"
        },
        "events": {
          "type": "array",
          "items": {
            "$ref": "#/components/schemas/CanonicalCaseEvent",
            "type": "object",
            "additionalProperties": false,
            "required": [
              "schemaVersion",
              "id",
              "cursor",
              "type",
              "occurredAt"
            ],
            "properties": {
              "schemaVersion": {
                "type": "string",
                "const": "case-event-v1"
              },
              "id": {
                "type": "string"
              },
              "cursor": {
                "type": "string",
                "description": "Opaque audit ID identifying a monotonically advancing committed per-case position. Never interpret or compare cursor text."
              },
              "type": {
                "type": "string"
              },
              "occurredAt": {
                "type": "string",
                "format": "date-time"
              }
            }
          }
        },
        "nextCursor": {
          "type": [
            "string",
            "null"
          ]
        },
        "hasMore": {
          "type": "boolean"
        }
      }
    },
    "requestId": {
      "type": "string"
    }
  }
}
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": {
    "schemaVersion": "case-event-page-v1",
    "caseId": "pcase_test_123",
    "events": [
      {
        "schemaVersion": "case-event-v1",
        "id": "id_test",
        "cursor": "cursor_test",
        "type": "type_test",
        "occurredAt": "2026-08-09T12:00:00.000Z"
      }
    ],
    "nextCursor": null,
    "hasMore": false
  },
  "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.