---
title: "Retrieve automation blocker"
method: GET
path: "/api/v1/automation_blockers/{id}"
tags: ["Automation Blocker"]
---

# Retrieve automation blocker

`GET /api/v1/automation_blockers/{id}`

Retrieve a specific automation blocker object.

## Path parameters

- `id` integer, required

## Response `200`

OK

- AutomationBlocker
  - `id` integer, required — AutomationBlocker object ID
  - `url` string, uri, required — AutomationBlocker object URL
  - `annotation` string, uri, required — URL of related Annotation object
  - `content` object[], required — List of reasons why automation is blocked
    - `level` 'datapoint' | 'annotation' — Designates whether automation blocker relates to specific `datapoint` or to the whole `annotation`
    - `type` 'automation_disabled' | 'is_duplicate' | 'suggested_edit_present' | 'low_score' | 'failed_checks' | 'no_validation_sources' | 'error_message' | 'delete_recommendation_filename' | 'delete_recommendation_page_count' | 'delete_recommendation_field' | 'extension' | 'human_confirmation_required' | 'alternative_prediction' — Type of automation blocker
    - `schema_id` string, nullable — Only for `datapoint` level objects
    - `samples` object[]
      - `datapoint_id` integer — ID of the datapoint
      - `details` object — Additional details specific to the blocker type
    - `samples_truncated` boolean, nullable — Whether number samples were truncated to 10, or contains all of them
    - `details` object, nullable — Only for `level`: `annotation` with `type`: `error_message` or `alternative_prediction`.
      - `message_content` string[] — List of error messages

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