Skip to main content
POST
/
v1
/
w3s
/
users
/
email
/
resendOTP
Resend an OTP email to the user
curl --request POST \
  --url https://api.circle.com/v1/w3s/users/email/resendOTP \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-User-Token: <x-user-token>' \
  --data '
{
  "idempotencyKey": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
  "otpToken": "eyJhbGciOiJS...-F8EFYDYjAxIUw",
  "email": "john@domain.com",
  "deviceId": "018d7c79-6b79-71ec-8ad8-ebc2b57a4650"
}
'
{
  "data": {
    "otpToken": "eyJhbGciOiJS...-F8EFYDYjAxIUw"
  }
}

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are required to make a successful request.

Headers

​
X-User-Token
string
required

Unique system generated JWT session token for specific user.

​
X-Request-Id
string<uuid>

Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. Must be a UUID to appear in logs. Non-UUID values are accepted by the API but are ignored by logging and tracing systems.

A unique identifier, which can be helpful for identifying a request when communicating with Circle support.

Example:

"2adba88e-9d63-44bc-b975-9b6ae3440dde"

Body

application/json

Request body

​
idempotencyKey
string<uuid>
required

Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. To create a UUIDv4 go to uuidgenerator.net. If the same key is reused, it will be treated as the same request and the original response will be returned.

Example:

"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"

​
otpToken
string
required

The OTP is bound on a user and purpose, and uses this value to identify the request.

Example:

"eyJhbGciOiJS...-F8EFYDYjAxIUw"

​
email
string
required

Sends OTP email to the destination address.

Example:

"john@domain.com"

​
deviceId
string
required

Get the device id from SDK, and the deviceToken is bound with this device id.

Example:

"018d7c79-6b79-71ec-8ad8-ebc2b57a4650"

Response

Successfully resent the OTP email.

​
data
object
required