---
title: "Report that verifications were fraudulent"
method: POST
path: "/fraud/report"
tags: ["fraudReporting"]
---

# Report that verifications were fraudulent

`POST /fraud/report`

Report verifications that you identified as connected to consumers who fraudulently attempted to verify for your offer (e.g. consumers who attempted to verify more than the allowed number of times or who were approved under false pretenses). This feedback will be used by SheerID to improve verification accuracy.

## Request body

- FraudReportRequest — The necessary data to report one or more verifications as fraudulent
  - `verificationIds` string[], required — The verificationIds to be reported as fraud

## Response `200`

The verifications were reported as fraudulent. Returns an empty body.

## Other responses

- `400` — Bad request - one or more required fields were not supplied, or were improperly formatted
- `401` — Unauthorized. The user is nor permitted to perform this action.
- `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)