Starts a dedicated bounced-email recovery flow. Sends a verification code to the replacement email without requiring verification of the old bounced email address.
curl --request POST \
--url https://api.fluxer.app/v1/users/@me/email-change/bounced/request-new \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"new_email": "jsmith@example.com"
}
'{
"ticket": "<string>",
"new_email": "<string>",
"new_code_expires_at": "<string>",
"resend_available_at": "<string>"
}Bot token: Authorization: Bot <token>. This is the primary authentication method for bot applications.
Success
Ticket associated with the email change attempt
The new email address the user wants to verify
ISO8601 timestamp when the new email code expires
ISO8601 timestamp when the new email code can be resent
curl --request POST \
--url https://api.fluxer.app/v1/users/@me/email-change/bounced/request-new \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"new_email": "jsmith@example.com"
}
'{
"ticket": "<string>",
"new_email": "<string>",
"new_code_expires_at": "<string>",
"resend_available_at": "<string>"
}