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

# Stores consumer info more permanently

`GET /verification/{verificationId}/rememberMeCallToAction`

Only for verifications with Remember Me enabled. After verification success, this endpoint can be used to determine what fields were collected during verification so that the consumer can be informed about which fields will be saved should they elect to have their information stored for future verifications.  This is often followed by a POST to `/verification/{verificationId]/rememberConsumer`

## Path parameters

- `verificationId` string, required

## Response `200`

The request has been accepted.

- RememberMeCallToActionResponse — After a verification is completed, this indicates what fields were collected during verification and whether there is an opportunity for the consumer to elect to have that information stored for future verifications.
  - `verificationId` string, required — The unique ID for the verification.
  - `alreadyRemembered` boolean, required — Indicates whether the consumer is already in our Remember Me database.
  - `collectedInformation` object, required — The personal information fields that was collected from the consumer during verification.
    - `collectedFields` string[] — The list of names of the person fields that were collected from the consumer.
    - `organization` Organization — An organization that can be used for instant verification of various segments (Student, Teacher, Military, etc.)
      - `name` string, required — The name of the organization
      - `id` integer, required — The unique identifier for the organization. This will be ignored if idExtended is specified.
      - `idExtended` string — The unique identifier for the Organization within the Organization service.
      - `source` 'EMPLOYER' | 'PLACE' — An identifier used for disambiguating the service which is providing the organization information.

## Other responses

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