---
title: "Split annotation"
method: POST
path: "/api/v1/annotations/{annotationID}/split"
tags: ["Annotation"]
---

# Split annotation

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

Splits an annotation into multiple separate annotations by reorganizing and possibly also rotating its pages.
Each resulting annotation will have its own document with the specified pages.

When using this endpoint, status of the original annotation is switched to `split`, status of the newly created
annotations is `importing` and the extraction phase begins over again.

This endpoint can be used for splitting annotations also from webhook listening to `annotation_content.initialize`
event and action.

## Path parameters

- `annotationID` integer, required

## Request body

- object
  - `documents` object[], required — List of [documents](/api/document) that should be created from the original annotation.
    - `pages` object[], required — List of [pages](/api/page) to include in this document
      - `page` string, uri, required — URL reference to the page
      - `rotation_deg` 0 | 90 | 180 | 270 — Rotation to apply to the page in degrees
    - `metadata` EditMetadata — Metadata will be saved in created/edited annotation/document metadata.
      - `annotation` object
      - `document` object

## Response `200`

Annotation split successfully

- object
  - `results` object[]
    - `annotation` string, uri — URL of the created annotation
    - `document` string, uri — URL of the created document.

## 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)