POSTpartial

Open the case this account already accepted on People's Court

Account branch, selected by a People's Court account access token with filings:write. The only inputs are the draft id in the path and the caller's idempotency key. In one guarded operation the server resolves the draft's owner (which must be the token principal), the recorded hosted_clickwrap acceptance by that principal for the draft's current digest, the applicable fee state, the current OAuth authority and the connector enablement policy, then invokes the shared case opening operation with commit-authorization proofs for the user, the OAuth token and grant, the authorizing client and the filing packet. The server consumes the recorded acceptance and never synthesizes one from arguments; no terms digest, acceptance statement, confirmation reference or principal is accepted here. Authentication and ownership precede replay lookup. A modified or expired packet returns acceptance_required and no persisted effect. That refusal is expected while the person is still reviewing, so it does not invalidate the page they already have open: it returns the packet and the issued link's acceptanceLinkExpiresAt, and carries a hostedAcceptanceUrl only when the issued link can no longer be used or when the request asked for a replacement. A payable filing fee returns filing_fee_required and opens nothing, because this branch initiates no payment. A response lost after commit is recoverable without opening a second case, including under a new idempotency key and after a token refresh. The partner branch is unchanged.

/api/filings/{id}/confirmationsconfirmAccountFiling

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.

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"}
Idempotency-KeyheaderRequired{"type":"string","minLength":8,"maxLength":200}

Request body

Optional request body.

application/json

{
  "type": "object",
  "additionalProperties": false,
  "description": "The confirmation carries no acceptance argument. No terms digest, acceptance statement, confirmation reference or principal is accepted; the acceptance is the one already recorded on People's Court.",
  "properties": {
    "rotateAcceptanceLink": {
      "type": "boolean",
      "description": "Replace the one-use hosted acceptance link on an acceptance_required refusal. Ask for this only when the person reports a lost link; the previous link stops working."
    }
  }
}

Responses

201

The case opened from this accepted packet, or the same case on a replay.

application/json

{
  "type": "object",
  "required": [
    "data",
    "requestId"
  ],
  "properties": {
    "data": {
      "$ref": "#/components/schemas/AccountOpenedCase",
      "type": "object",
      "description": "The case this account-owned packet opened. Show-once party capabilities are never returned to an application.",
      "properties": {
        "schemaVersion": {
          "type": "string",
          "const": "account-filing-v1"
        },
        "filingId": {
          "type": "string"
        },
        "caseId": {
          "type": "string"
        },
        "status": {
          "type": "string"
        },
        "filingFeePending": {
          "type": "boolean"
        },
        "track": {
          "type": "string"
        },
        "noticeQueued": {
          "type": "boolean"
        },
        "noticeAddressMasked": {
          "type": "string"
        },
        "acceptance": {
          "type": "object",
          "required": [
            "method",
            "termsDigest"
          ],
          "properties": {
            "method": {
              "type": "string",
              "const": "hosted_clickwrap"
            },
            "termsDigest": {
              "type": "string"
            },
            "attestationHash": {
              "type": "string"
            }
          }
        },
        "links": {
          "type": "object",
          "required": [
            "casePage"
          ],
          "properties": {
            "casePage": {
              "type": "string"
            }
          }
        },
        "idempotencyReplayed": {
          "type": "boolean"
        }
      },
      "required": [
        "schemaVersion",
        "filingId",
        "caseId",
        "status",
        "filingFeePending",
        "track",
        "noticeQueued",
        "acceptance",
        "links",
        "idempotencyReplayed"
      ]
    },
    "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": "account-filing-v1",
    "filingId": "filingId_test",
    "caseId": "pcase_test_123",
    "status": "status_test",
    "filingFeePending": false,
    "track": "track_test",
    "noticeQueued": false,
    "acceptance": {
      "method": "hosted_clickwrap",
      "termsDigest": "termsDigest_test"
    },
    "links": {
      "casePage": "casePage_test"
    },
    "idempotencyReplayed": 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.
  • 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.