---
title: "Edit annotation (legacy split)"
method: POST
path: "/api/v1/annotations/{annotationID}/edit"
tags: ["Annotation"]
---

# Edit annotation (legacy split)

`POST /api/v1/annotations/{annotationID}/edit`

Legacy endpoint for splitting annotations. Creates new annotations from the original annotation's pages.

<Callout type="info">
This is a legacy endpoint. For new implementations, use the [split](/api/annotation#split-annotation)
endpoint instead, which provides the same functionality with a clearer name.
</Callout>

If used on an annotation in a way that after the editing only one document remains, the original annotation will
be edited. If multiple documents are to be created after the call, status of the original annotation is switched
to `split`, status of the newly created annotations is `importing` and the extraction phase begins over again.

## Path parameters

- `annotationID` integer, required

## Request body

- object
  - `documents` object[], required — Array of documents to create
    - `pages` EditPage[], required — Pages to include in this document
      - `page` string, uri, required — Page URL
      - `rotation_deg` 0 | 90 | 180 | 270 — Rotation to apply in degrees
      - `deleted` boolean — Indicates whether the page is marked as deleted.
    - `metadata` EditMetadata — Metadata will be saved in created/edited annotation/document metadata.
      - `annotation` object
      - `document` object

## Response `200`

Annotation edited successfully

- EditPagesResult
  - `results` object[] — Created or modified annotations
    - `annotation` string, uri — Annotation URL
    - `document` string, uri — Document URL

## Other responses

- `400` — Invalid input data.
- `401` — The username/password is invalid or token is invalid (e.g. expired).
- `403` — Insufficient permission, missing authentication, invalid CSRF token and similar issue.
- `404` — The specified resource was not found.
- `413` — Payload too large (especially for files uploaded).
- `429` — Request rate is too high, wait before sending more requests. See [Rate Limiting](/guides/overview#rate-limiting) for more details.
- `500` — Server failure while processing the request.
- `502` — Invalid response from the upstream server.
- `503` — We're temporarily offline for maintenance. Please try again later.
- `504` — Upstream server could not complete the request in time.

---

[API](https://skmtc.dev/rossum/apis/rossum-api.md) · [All operations](https://skmtc.dev/rossum/apis/rossum-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rossum/rossum-api/revisions/f1b5a910991d/schema)