> For the complete documentation index, see [llms.txt](https://peoplescourt.ai/llms.txt). This page is also available as Markdown.

# Contract policy

The People’s Court API keeps operation IDs and request and response contracts stable. The [endpoint reference](https://peoplescourt.ai/docs/api/reference.md) describes the supported operations, credentials and schemas.

## Additive changes

New optional fields and operations preserve existing requests and consumers. Ignore unknown object fields and tolerate documented extensible values. Accepted consent, signed artifacts and case-pinned Rules are never reinterpreted. Adding required input, narrowing authorization, changing response types or removing enum values is a breaking change.

## Breaking changes and operation IDs

Breaking changes are announced with the affected operations, required client changes and effective dates. Operation IDs are not repurposed. Consult the [changelog](https://peoplescourt.ai/docs/api/changelog.md) when maintaining an integration.

## Webhooks

Webhook event schemas are versioned in the published contract. Event IDs, signing inputs, signature verification and replay semantics stay stable for the subscribed schema. A breaking payload uses a separately documented schema; subscriptions are never switched silently. Callbacks are delivered at least once: deduplicate by event ID and fetch authoritative state. A callback does not establish payment or change recorded case service.

## Rules and consent

Each case keeps the exact Rules and procedure terms its parties accepted. Read the current Rules for each filing and obtain the required acceptance of its review packet. API access does not supply arbitration consent or an appeal waiver.