---
title: "Update proposed changes on a Draft amendment"
method: PATCH
path: "/api/v1/legal_entities/{id}/amendments/{filingId}"
tags: ["Entity filings"]
---

# Update proposed changes on a Draft amendment

`PATCH /api/v1/legal_entities/{id}/amendments/{filingId}`

Only `Draft` filings can be changed. Omitted fields are preserved; null clears a proposal. A revision invalidates the previous signature. Invoiced and submitted filings are read-only. Standard keys act on every entity the key owner actively represents. Agent Keys are limited to entities incorporated through the API and need active representation and the listed `agent:entity.filing.*` scope. Agent writes also require an active Manifestation of Will. OAuth tokens and Partner Keys cannot call these filing endpoints. See https://docs.eprospera.com/entity-filings for signing, payment, and recovery. Agent scope: `agent:entity.filing.create`.

Account deactivation revokes personal API keys, including Agent Keys, and OAuth authorizations. Account reactivation requires new API keys, including new Agent Keys, and consent; previously issued credentials remain invalid.

## Path parameters

- `id` string, uuid, required
- `filingId` string, uuid, required

## Request body

- AmendmentPatchRequest — PATCH preserves omitted fields; explicit null clears a proposed change. Any revision invalidates the previous signature.
  - `updatedName` string, nullable
  - `updatedExtension` string, nullable
  - `updatedNameStartsWithExtension` boolean, nullable
  - `updatedAddress` object, nullable
    - `line1` string, required
    - `line2` string, nullable
    - `city` string, required
    - `state` string, nullable
    - `postalCode` string, required
    - `country` string, required

## Response `200`

Updated amendment draft.

- AmendmentFilingResponse
  - `data` AmendmentFiling, required
    - `id` string, uuid, required
    - `legalEntityId` string, uuid, required
    - `statusId` 'Draft' | 'Pending Payment' | 'Pending Review' | 'Approved' | 'Rejected', required — Draft: editable; may be signed before invoice preparation. Pending Payment: signed and invoiced. Pending Review: paid and submitted. Approved: changes applied to the registry. Rejected: declined with a reason.
    - `proposedChanges` object, required
      - `name` string, nullable, required
      - `extension` string, nullable, required
      - `nameStartsWithExtension` boolean, nullable, required
      - `principalOfficeAddress` Address, nullable, required
        - `line1` string, required
        - `line2` string, nullable
        - `city` string, required
        - `state` string, nullable
        - `postalCode` string, required
        - `country` string, required
    - `signed` boolean, required
    - `signedAt` string, date-time, nullable, required
    - `invoice` FilingInvoice, nullable, required
      - `id` string, uuid, required
      - `statusId` string, required — Invoice status, for example `open` or `paid`.
    - `submittedAt` string, date-time, nullable, required
    - `approvedAt` string, date-time, nullable, required
    - `rejectedAt` string, date-time, nullable, required
    - `rejectedReason` string, nullable, required
    - `createdAt` string, date-time, required
    - `updatedAt` string, date-time, required
    - `nextSteps` AmendmentNextSteps, required
      - `changesRequired` boolean, required — True while the open filing has no proposed changes.
      - `signatureUrl` string, uri, nullable, required — Portal page where an active representative signs the amendment. Null once signed or after submission. Signing requires a portal login; the API never accepts signature images.
      - `paymentRequired` boolean, required — True for an open Draft or Pending Payment filing whose invoice is not paid. False on terminal states is not independent proof of settlement.
      - `reviewDispatchPending` boolean, required — The submission is saved and its review event is awaiting delivery. Safe to retry submit; background recovery also retries.
      - `submitReady` boolean, required — True when the filing is signed and paid but not yet submitted. Voucher payments submit automatically.
  - `nextSteps` AmendmentNextSteps, required
    - `changesRequired` boolean, required — True while the open filing has no proposed changes.
    - `signatureUrl` string, uri, nullable, required — Portal page where an active representative signs the amendment. Null once signed or after submission. Signing requires a portal login; the API never accepts signature images.
    - `paymentRequired` boolean, required — True for an open Draft or Pending Payment filing whose invoice is not paid. False on terminal states is not independent proof of settlement.
    - `reviewDispatchPending` boolean, required — The submission is saved and its review event is awaiting delivery. Safe to retry submit; background recovery also retries.
    - `submitReady` boolean, required — True when the filing is signed and paid but not yet submitted. Voucher payments submit automatically.

## Other responses

- `400` — Validation error or precondition failure.
- `401` — Missing or invalid credential.
- `403` — Credential lacks the required scope (Agent Key) or insufficient OAuth scope.
- `404` — Resource does not exist or is invisible to the caller. The two are intentionally indistinguishable.
- `409` — Conflicting state (e.g. legal-entity name already taken).
- `429` — Rate limit exceeded. No `Retry-After` header is currently emitted; back off exponentially.
- `500` — Server error.

## Changes

- **2026-09-22** `d2c5a5cda002` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/eprospera/apis/e-pro-spera-api/changes/api/v1/legal_entities/:id/amendments/:filingId/patch.md)

---

[API](https://skmtc.dev/eprospera/apis/e-pro-spera-api.md) · [All operations](https://skmtc.dev/eprospera/apis/e-pro-spera-api/llms.txt) · [OpenAPI document](https://skmtc.dev/eprospera/apis/e-pro-spera-api/revisions/6fbf9c9b36b5?raw)