---
title: "check user"
method: POST
path: "/check-user"
tags: ["Authentication"]
---

# check user

`POST /check-user`

Check if a user is already registered to this campaign with a specific email address. This is useful for validation in a sign-up form to prompt an existing user to log in.
#### For custom components:
`RaiselyComponents.api.all('check-user').post(data = {}, params = {}, headers = {}) => Promise<{result}>`

 :fa-gears: See [Restie Response Data](https://github.com/raisely/restie#reading-and-handling-responses) for a more detailed overview of responses through the client wrapper

## Headers

- `Authorization` string

## Request body

- object
  - `data` object, required
    - `email` string, required — Email of the user
  - `campaignUuid` string, required — The UUID of the campaign to check

## Response `200`

The response will indicate if the user is `OK` and can sign up to the campaign, or if they `EXIST` and should log in.

- object
  - `status` string — Contains 'EXISTS' if the user exists and has a profile. Otherwise 'OK' (including if they exist, but have no profile)
  - `emailVerified` boolean — Only present when the ZR0_1845_MAGIC_LINK_VERIFICATION feature flag is enabled. Indicates whether the user has verified their email (i.e. has set a password).

## Other responses

- `401` — Authorization credentials were missing or invalid
- `403` — The user is authenticated, but is not allowed to perform the requested operation
- `410` — The requested record no longer exists, or that API has been deprecated
- `429` — You have made too many requests to the given endpoint, please try again later
- `500` — An unexpected error has occurred with Raisely. If the error persists you can contact support@raisely.com

---

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