POST
/
auth
/
user-auth
/
resend-otp
curl --request POST \
  --url https://external.dev.onboardpay.co/auth/user-auth/resend-otp \
  --header 'Content-Type: application/json' \
  --header 'x-signature: <api-key>' \
  --data '{
  "authSessionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}'
{
  "sent": true,
  "authSessionId": "<string>"
}

Resends the OTP to the user’s email for authentication during sign-in or sign-up. Use this if the previous OTP was not received by the user, or has expired.

This endpoint is specifically for user authentication (logging in or signing up).

Do not confuse it with the 2FA OTP endpoint, which generates OTPs for verifying sensitive account actions (e.g., updating payment methods).

Authorizations

​
x-signature
string
header
required

Body

application/json

Response

200
application/json

Success

The response is of type object.

POST
/
auth
/
user-auth
/
resend-otp
curl --request POST \
  --url https://external.dev.onboardpay.co/auth/user-auth/resend-otp \
  --header 'Content-Type: application/json' \
  --header 'x-signature: <api-key>' \
  --data '{
  "authSessionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}'
{
  "sent": true,
  "authSessionId": "<string>"
}

Resends the OTP to the user’s email for authentication during sign-in or sign-up. Use this if the previous OTP was not received by the user, or has expired.

This endpoint is specifically for user authentication (logging in or signing up).

Do not confuse it with the 2FA OTP endpoint, which generates OTPs for verifying sensitive account actions (e.g., updating payment methods).

Authorizations

​
x-signature
string
header
required

Body

application/json

Response

200
application/json

Success

The response is of type object.