Respond for a party

Use this flow when you represent the respondent in an existing case. Respondent authority does not authorize opening the claimant’s complaint. Obtain the case or filing ID through the authorized handoff; do not enumerate cases.

Step	Actor and request	Expected result and next action	Interruption
Establish participation	An invited person follows the hosted handoff, or an independently integrated respondent reads `GET /api/filings/{id}` and confirms its own participant requirement through `POST /api/filings/{id}/confirmations` when bilateral confirmation is required.	A case-bound respondent membership after the required acceptance.	Wrong principal, revoked authority, expired credentials, or a consumed invitation cannot be repaired by asserting another side in the body.
Read the case	Respondent: `GET /api/cases/{id}` with its bearer credential and authorized membership or existing case capability.	The respondent’s deadlines, next actions, and current revision.	A read-only membership cannot file an Answer or later submission.
Answer	Respondent: `POST /api/cases/{id}/answer` with the exact required agreement, principal and actor provenance, typed Answer and requested relief, and an idempotency key.	Consent, participation, and the Answer commit under the case’s pinned procedure. Refresh the case view.	If notice or acceptance is still required, complete the returned prerequisite first. A conflicting revision requires review of the current case.
File later material	Multipart `POST /api/cases/{id}/submissions` with `x-pc-party: respondent`, respondent attestation, and an idempotency key while the action is available.	A committed evidence or rebuttal filing.	Simultaneous exchange keeps the opponent’s sealed material unavailable until disclosure.
Review and confirm	`GET /api/cases/{id}/record-summary`, then `POST /api/cases/{id}/record-summary/confirmations` with the exact digest and statement for the respondent.	The respondent’s record confirmation.	A changed source or expired review window requires refreshing the case; do not reuse an old digest.
Follow service	`GET /api/cases/{id}` and its authorized artifact links.	A served decision, any appeal opportunity, and execution state.	Read Follow the decision and execution before treating an Award as executable.

A claimant token cannot authorize respondent activity. Keep the same idempotency key and body when retrying a request whose outcome is unknown. A replay never repeats a show-once capability.

TypeScript SDK

Save SDK examples at the repository root. Pass the configured PeopleCourtClient from the quickstart, a case ID obtained through your authorized handoff, and a durable idempotency key for each distinct mutation.

import type { PeopleCourtClient, ApiCanonicalPartnerAnswerInput }
  from "./sdk/typescript/src/index.ts";

export async function answerForMember(client: PeopleCourtClient,
  caseId: string, input: ApiCanonicalPartnerAnswerInput, idempotencyKey: string) {
  const { data: view } = await client.getCasePreview(caseId);
  if (!view.availableActions.some(action => action.code === "answer")) {
    throw new Error("The respondent cannot file an Answer in this state.");
  }
  const answer = await client.fileAnswerPreview(caseId, input, idempotencyKey);
  const next = await client.getCasePreview(caseId);
  return { answer: answer.data, stage: next.data.stage, deadlines: next.data.deadlines };
}