> ## Documentation Index > Fetch the complete documentation index at: https://www.presolve.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Create a case > Creates a case (plus plaintiff and intake survey details) in the caller’s organization through the canonical write-once ownership command. Partner keys and OIDC bearers keep working unchanged; integration keys require cases:write and the standard X-Idempotency-Key contract. Requires the `cases:write` scope. Legacy partner API keys and OIDC bearer tokens are also accepted on this endpoint (shipped behavior, unchanged); integration keys are scope-enforced. Mutations require an `X-Idempotency-Key` header (responses are stored for replay; reusing a key with a different request returns 409 `IDEMPOTENCY_CONFLICT`). Rate tier: `write`. ## OpenAPI ````yaml /openapi.json post /api/v1/cases openapi: 3.1.0 info: title: Grand Charter Public API version: 1.0.0 description: >- Org-scoped integration API for the Grand Charter legal platform. Authenticate every request with an integration API key in the `x-api-key` header. Keys are created in the attorney portal under **Settings → Integrations → API Credentials** (or by platform admins) and carry an explicit list of scopes; each operation below names its required scope (`x-required-scope`). Conventions: JSON bodies/responses in camelCase; money in integer cents; ISO-8601 UTC timestamps; keyset cursor pagination (`after`, `limit` → `nextCursor`); errors use `{ success: false, error, code }`. Idempotency: most mutations require an `X-Idempotency-Key` header — each operation description below says so explicitly. Exceptions that do NOT consume the header (retrying them can create duplicates): `POST /leads`, `PATCH /leads/{leadId}`, and `PATCH /cases/{caseId}`. servers: - url: https://www.presolve.com description: Production security: - integrationApiKey: [] tags: - name: Platform - name: Org & Team - name: Cases - name: Leads - name: Clients - name: Contacts - name: Documents - name: Notes - name: Tasks - name: Calendar - name: Deadlines - name: Intake - name: E-Sign - name: Billing - name: Settlement Funds - name: Referrals - name: Communications - name: Medical - name: Reports & Exports - name: Events & Webhooks paths: /api/v1/cases: post: tags: - Cases summary: Create a case description: >- Creates a case (plus plaintiff and intake survey details) in the caller’s organization through the canonical write-once ownership command. Partner keys and OIDC bearers keep working unchanged; integration keys require cases:write and the standard X-Idempotency-Key contract. Requires the `cases:write` scope. Legacy partner API keys and OIDC bearer tokens are also accepted on this endpoint (shipped behavior, unchanged); integration keys are scope-enforced. Mutations require an `X-Idempotency-Key` header (responses are stored for replay; reusing a key with a different request returns 409 `IDEMPOTENCY_CONFLICT`). Rate tier: `write`. operationId: post_cases parameters: - name: X-Idempotency-Key in: header required: false description: >- Required for integration-key callers; optional for legacy partner-key/OIDC callers. schema: type: string maxLength: 200 requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/LegacyCaseCreateBody' responses: '201': description: '{ success: true, caseId }' content: application/json: schema: $ref: '#/components/schemas/SuccessEnvelope' '400': description: Validation failed (VALIDATION_FAILED). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing, invalid, or expired API key (UNAUTHORIZED). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: API key lacks the required scope (FORBIDDEN). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Resource not found in the caller’s organization (NOT_FOUND). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: >- Conflict: invalid state transition, duplicate entry, stale revision, or idempotency conflict. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Rate limit exceeded (RATE_LIMITED). Honor Retry-After. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - integrationApiKey: [] components: schemas: LegacyCaseCreateBody: type: object properties: firstName: type: string lastName: type: string email: type: string phone: type: string dateOfBirth: type: string zipCode: type: string city: type: string state: type: string description: type: string caseType: type: string subCaseType: type: string caseMatchMode: type: string enum: - attorney - plaintiff attorneyId: type: string matterStage: type: string matterStatus: type: string estimatedSettlementMin: type: number description: Dollars (converted to cents server-side) estimatedSettlementMax: type: number description: Dollars (converted to cents server-side) estimatedTimeToResolution: type: number dateOfIncident: type: string partnerId: type: string partnerName: type: string isCommercial: type: boolean highValue: type: boolean surveyDetails: type: object additionalProperties: anyOf: - type: string - type: number - type: boolean description: Intake survey answers keyed by accessor (max 200 keys) targetOrganizationId: type: string description: Partner keys with partner_multi_org only required: - firstName - lastName SuccessEnvelope: type: object properties: success: type: boolean const: true required: - success additionalProperties: {} ErrorResponse: type: object properties: success: type: boolean const: false error: type: string description: >- Human-readable error message. 5xx responses are always scrubbed to "Internal server error". code: type: string description: >- Stable machine-readable error code (ErrorCode), e.g. UNAUTHORIZED, FORBIDDEN, VALIDATION_FAILED, NOT_FOUND, INVALID_STATE_TRANSITION, DUPLICATE_ENTRY, STALE_REVISION, IDEMPOTENCY_IN_PROGRESS, IDEMPOTENCY_CONFLICT, RATE_LIMITED, INTERNAL_ERROR. required: - success - error - code securitySchemes: integrationApiKey: type: apiKey in: header name: x-api-key description: >- Org-issued integration API key (service account credential). The plaintext secret is shown once at creation. ````