---
title: "Stores consumer info more permanently"
method: POST
path: "/verification/{verificationId}/rememberConsumer"
tags: ["verification"]
---

# Stores consumer info more permanently

`POST /verification/{verificationId}/rememberConsumer`

Only for verifications with Remember Me enabled. Stores consumer info associated with the verification to be used for future verifications. Requires consent from consumer indicated in the request body.

## Path parameters

- `verificationId` string, required

## Request body

- RememberConsumerRequest — The consent information indicating whether the consumer has explicitly elected to opt in to have their PII more permanently stored.
  - `rememberMeConsentValue` boolean, required
  - `sheeridMarketingConsentValue` boolean — Indicates whether the consumer consents to marketing that originates from SheerID.

## Response `200`

The consent values were recorded. Returns an empty body.

## Other responses

- `400` — Bad request
- `404` — Verification not found
- `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)