---
title: "Request replacement email for bounced address"
method: POST
path: "/users/@me/email-change/bounced/request-new"
tags: ["Users"]
---

# Request replacement email for bounced address

`POST /users/@me/email-change/bounced/request-new`

Starts a dedicated bounced-email recovery flow. Sends a verification code to the replacement email without requiring verification of the old bounced email address.

## Request body

- EmailChangeBouncedRequestNewRequest
  - `new_email` string, email, required

## Response `200`

Success

- EmailChangeRequestNewResponse
  - `ticket` string, required — Ticket associated with the email change attempt
  - `new_email` string, required — The new email address the user wants to verify
  - `new_code_expires_at` string, required — ISO8601 timestamp when the new email code expires
  - `resend_available_at` string, nullable, required — ISO8601 timestamp when the new email code can be resent

## Other responses

- `400` — Bad Request - The request was malformed or contained invalid data
- `401` — Unauthorized - Authentication is required or the token is invalid
- `403` — Forbidden - You do not have permission to perform this action
- `429` — Too Many Requests - You are being rate limited
- `500` — Internal Server Error - An unexpected error occurred

---

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