For the complete documentation index, see llms.txt. This page is also available as Markdown.

POSTpartial

Accept an exact prepared filing as its designated principal

The designated principal explicitly accepts the exact packet. For a standing-bound OAuth token, amount, acts, transaction, procedure, clock and current terms are checked; standing consent and a principal notice commit atomically, and confirmation rechecks revocation. A personal-client grant cannot be applied by a preparing partner merely by knowing its ID.

/api/authorizations/consentsacceptAccountFilingPacket

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 approved scopes. S256 PKCE is mandatory on the code flow. Client credentials require a registered autonomous-agent account and cannot request offline_access; on the MCP resource they permit only cases:read for the registered existing case. Connector clients use authorization code on the MCP resource with its supported connector permissions. Explicit reacceptance is required after Rules or disclosure changes.

Parameters

This operation has no path, query, or header parameters.

Request body

Required request body.

application/json

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

Responses

201

Successful operation.

application/json

{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "accepted": {
          "const": true
        },
        "termsDigest": {
          "type": "string"
        },
        "attestationHash": {
          "type": "string"
        }
      }
    }
  }
}
default

Authorization failure; consent_required requires explicit reacceptance.

application/json

{
  "$ref": "#/components/schemas/AccountOAuthError",
  "type": "object",
  "properties": {
    "error": {
      "type": "string"
    },
    "error_description": {
      "type": "string"
    }
  },
  "required": [
    "error"
  ]
}

Example response

Successful response

{}

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.