# SES production access from the CLI | Changelog

Source: https://wraps.dev/changelog/ses-production-access-from-the-cli

![Wraps Logo](https://wraps.dev/wraps-light-logo.png)![Wraps Logo](https://wraps.dev/wraps-dark-logo.png)

](https://wraps.dev/)

[](https://github.com/wraps-team/wraps)[Log in](https://app.wraps.dev/auth?mode=signin)[Sign up](https://app.wraps.dev/auth?mode=signup)

Toggle menu

[← All changes](https://wraps.dev/changelog)

CLISeptember 2026

### SES production access from the CLI

Check where your SES production-access request stands, and file it from your terminal, with wraps email production-access.

-   Run `wraps email production-access` to see whether the account is still in the sandbox, AWS’s review status and case ID, and your daily quota. It changes nothing
-   Add `--request` with `--website` and `--mail-type` to file the request with your own AWS credentials. The command asks for confirmation first, or takes `--yes` in scripts, and refuses if access is already enabled or a review is pending
-   The API sends less than the console form. It has no field for the acknowledgment that your recipients opted in and that you handle bounces and complaints, so make sure both are true before you submit, or use the console link the command prints
-   Your credentials need `ses:GetAccount` and `ses:PutAccountDetails`. AWS still reviews every request by hand, usually within 24 hours

CLI v3.13.0

[Read the docs →](https://wraps.dev/docs/guides/production-access)