POSTpartial

Accept Agent-only procedure as the verified principal

Exact packet digest and side-specific statement required. Both principals must accept independently before a representative can open the case. Acceptance and OAuth/account guards commit atomically.

/api/filings/{id}/agent-consentsacceptAgentOnlyFiling

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

Request body

Required request body.

application/json

{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "termsDigest",
    "acceptanceStatement"
  ],
  "properties": {
    "termsDigest": {
      "type": "string"
    },
    "acceptanceStatement": {
      "type": "string"
    }
  }
}

Responses

200

Authorized operation result.

application/json

{
  "$ref": "#/components/schemas/CanonicalAcceptAgentOnlyFilingResponse",
  "type": "object",
  "required": [
    "data",
    "requestId"
  ],
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "accepted": {
          "const": true
        },
        "side": {
          "type": "string",
          "enum": [
            "claimant",
            "respondent"
          ]
        },
        "termsDigest": {
          "type": "string"
        }
      },
      "required": [
        "accepted",
        "side",
        "termsDigest"
      ]
    },
    "requestId": {
      "type": "string"
    }
  },
  "x-code-source": "app/api/filings/[id]/agent-consents/route.ts"
}
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": {
    "accepted": true,
    "side": "claimant",
    "termsDigest": "termsDigest_test"
  },
  "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.
  • The request is accepted only when its credential, authority, case state, and resource preconditions are satisfied.