---
title: "Generate verification report for re-verification task"
method: POST
path: "/report/reverify/{batchId}"
tags: ["report"]
---

# Generate verification report for re-verification task

`POST /report/reverify/{batchId}`

Generate a verification report for a re-verification task which can be downloaded later

## Path parameters

- `batchId` string, required

## Response `202`

Accepted

- ReportStatusResponse
  - `id` string
  - `status` 'PENDING' | 'COMPLETE' | 'ERROR' | 'DELETED'
  - `statusUrl` string, uri
  - `retrievalUrl` string, uri, nullable — The URL to download the completed report from. The value is `null` until the status of the report becomes `COMPLETE`.
  - `requester` string
  - `created` integer

## Other responses

- `401` — Unauthorized
- `429` — Too many requests. A `429` can mean one of two things — inspect the response body's `errorIds` before retrying: - A transient rate limit applied at the platform edge. If a `Retry-After` header is present, wait that many seconds (using exponential backoff) and retry. - A program/consumer limit such as `verificationLimitExceeded`, `reverificationDailyLimitExceeded`, or `docReviewLimitExceeded` — the consumer has exhausted an allowance defined by the program's limiting policy. This is a permanent rejection (`currentStep: error`, no `Retry-After`); do not retry.
- `500` — Internal server error.
- `503` — Service temporarily unavailable. The request can be safely retried after the interval given in the `Retry-After` header.

---

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