Send an email verification code to the signed-in user
Needs a login token for the org.
POST/api/v1/auth/users/send-email-verification-code
- Sign-in
- A login token from hosted sign-in as a Bearer token, and the organization in the state header or the org query parameter.
- Rate limit
- Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 10 requests a minute per IP address.
- Request body
- None: send the request without a body.
Needs a login token for the org. Answers Email Already verified. when the token says the email is verified, and 429 EMAIL_RECIPIENT_LIMIT when the recipient limit is reached.
Request
This operation takes no parameters and no body.
Example request
Replace each YOUR_... value with your own, and set the credential in the environment variable the sample reads.
curl -X POST "https://api.console.buildbase.app/api/v1/auth/users/send-email-verification-code?org=YOUR_ORG_ID" \
-H "Authorization: Bearer $BUILDBASE_LOGIN_TOKEN"const response = await fetch(
'https://api.console.buildbase.app/api/v1/auth/users/send-email-verification-code?org=YOUR_ORG_ID',
{
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.BUILDBASE_LOGIN_TOKEN}`,
},
}
);
if (!response.ok) {
throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.json();import os
import requests
response = requests.post(
"https://api.console.buildbase.app/api/v1/auth/users/send-email-verification-code?org=YOUR_ORG_ID",
headers={
"Authorization": "Bearer " + os.environ["BUILDBASE_LOGIN_TOKEN"],
},
timeout=30,
)
response.raise_for_status()
data = response.json()Responses
200 OK
OK
{
"message": "Verification Email Sent successfully.",
"success": true
}Any other status
Any other answer the handler sends itself (its own refusals). Not described yet.
Errors
Each refusal, what it means, and what to do. The request changed nothing.
400 Bad Request
What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.
What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.
{
"error": true,
"success": false,
"path": "string",
"message": "string"
}401 Unauthorized
What it means: The credential is missing, expired or not accepted here, or the caller's role has no grant for x-permission (refused with 401 too). The body is the plain text Unauthorized, or a JSON body with a code where the gate says why.
What to do: Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.
Unauthorized429 Too Many Requests
What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.
What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.
{
"success": false,
"message": "string",
"reason": "rate_limited",
"retryAfter": 1
}Related
- Auth guide: how this part of BuildBase works
- All Auth operations
- API reference: every operation, by tag
- Sign-in and credentials for the HTTP API
- How the HTTP API reports errors
- Make your first call
- Error codes: every
codethe API returns - OpenAPI: operation
auth.users.sendEmailVerificationCode.createin public-v1.json