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

POSTpartial

File a challenge under the case-pinned historical AI-configuration procedure

Only a case-bound party or authorized representative may file. Current Rules reject this historical procedure. The response retains the hosted ok/data or ok/error/code envelope and carries the filing party's scoped case projection. Administrative resolution remains an internal restricted act.

/api/cases/{id}/ai-configuration-challengesfileHistoricalAiConfigurationChallengeCanonical

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.

CanonicalSession

The signed-in account’s session. Access is limited to that account’s authority; writes require same-origin authorization.

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

NameLocationRequirementSchema
idpathRequired{"type":"string"}

Request body

Required request body.

application/json

{
  "type": "object",
  "required": [
    "expectedRevision",
    "concern"
  ],
  "properties": {
    "expectedRevision": {
      "type": "integer"
    },
    "concern": {
      "type": "string",
      "enum": [
        "provider_is_party",
        "operator_is_party",
        "developer_is_party",
        "controlling_affiliate_is_party",
        "direct_material_economic_interest",
        "material_subject_integrity_risk",
        "data_incompatibility",
        "integrity_defect",
        "configuration_unavailable",
        "generic_ai"
      ]
    },
    "detail": {
      "type": "string"
    }
  }
}

Responses

201

Challenge stored under the pinned historical procedure.

application/json

{
  "type": "object",
  "properties": {
    "ok": {
      "const": true
    },
    "data": {
      "type": "object",
      "properties": {
        "status": {
          "const": "committed"
        },
        "dispute": {
          "type": "object",
          "properties": {
            "id": {
              "type": "string"
            },
            "status": {
              "type": "string"
            },
            "revision": {
              "type": "integer"
            },
            "aiConfigurationChallenges": {
              "type": "array",
              "items": {
                "type": "object",
                "properties": {
                  "id": {
                    "type": "string"
                  },
                  "concern": {
                    "type": "string"
                  },
                  "detail": {
                    "type": "string"
                  },
                  "filedBySide": {
                    "type": "string",
                    "enum": [
                      "claimant",
                      "respondent"
                    ]
                  },
                  "filedAt": {
                    "type": "string"
                  },
                  "status": {
                    "type": "string"
                  },
                  "resolution": {
                    "type": "object",
                    "properties": {
                      "at": {
                        "type": "string"
                      },
                      "actorLabel": {
                        "type": "string"
                      },
                      "reasons": {
                        "type": "string"
                      },
                      "replacementSelected": {
                        "type": "boolean"
                      }
                    }
                  }
                }
              }
            }
          }
        },
        "challenge": {
          "type": "object",
          "properties": {
            "id": {
              "type": "string"
            },
            "concern": {
              "type": "string"
            },
            "detail": {
              "type": "string"
            },
            "filedBySide": {
              "type": "string",
              "enum": [
                "claimant",
                "respondent"
              ]
            },
            "filedAt": {
              "type": "string"
            },
            "status": {
              "type": "string"
            },
            "resolution": {
              "type": "object",
              "properties": {
                "at": {
                  "type": "string"
                },
                "actorLabel": {
                  "type": "string"
                },
                "reasons": {
                  "type": "string"
                },
                "replacementSelected": {
                  "type": "boolean"
                }
              }
            }
          }
        }
      },
      "required": [
        "status",
        "dispute",
        "challenge"
      ]
    }
  },
  "required": [
    "ok",
    "data"
  ]
}
default

Unchanged hosted error envelope; authority, revision and historical Rules restrictions apply.

application/json

{
  "type": "object",
  "properties": {
    "ok": {
      "const": false
    },
    "error": {
      "type": "string"
    },
    "code": {
      "type": "string"
    }
  }
}

Example response

Successful response

{
  "ok": true,
  "data": {
    "status": "committed",
    "dispute": {},
    "challenge": {}
  }
}

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.