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

# Approve annotation

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

Approve annotation, switch its status to `exporting` or `confirmed`, or it stays in `in_workflow`, depending on the evaluation of the current [workflow step](/api/workflow-step).

<Callout type="info">
Approving is allowed only for documents in states: `in_workflow`. See [Annotation Lifecycle](/guides/annotation-lifecycle) for more information about states.
</Callout>

Only admin, organization group admin, or an assigned user with approver role can approve annotation in this state. A [workflow activity](/api/workflow-activity) record object will be created.

<Callout type="info">
Talk with a Rossum representative about enabling this feature. Read more about [workflows](/guides/workflow-guide).
</Callout>

## Request body

- object

## Response `200`

OK

- object
  - `status` string — New status of the annotation.

## 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.
- `409` — Conflict
- `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)