> For the complete Lynkow documentation index in agent-friendly format, see [llms.txt](/llms.txt).

# Preserve resend-verification compatibility

**Publié le** : 2026-08-19
**Catégorie** : Commerce

## `POST /customers/resend-verification`

**Preserve resend-verification compatibility**

Preserves the published resend-verification endpoint as an authenticated
204 No Content no-op in every reachable state. It neither replaces a
verification token nor dispatches email. Requires a valid customer
session token; a missing or invalid token returns 401 with error code
`CUSTOMER_AUTH_REQUIRED`. The optional `locale` body field remains
accepted for compatibility but does not change the no-op behavior.

### Request Body

Content-Type: `application/json`

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `locale` | string | No | Accepted for wire compatibility but has no effect on this authenticated 204 no-op |


### Responses

| Status | Description |
| --- | --- |
| `204` | No content |
| `401` | Missing or invalid storefront publishable key |
| `402` | The site subscription does not currently permit this operation |
| `403` | The storefront key origin is not allowed |
| `404` | Site, resource, or commerce feature not found |
| `422` | Validation error |


> **Notes:** The customer-auth and storefront throttle buckets can return 429 with
> `RATE_LIMIT_EXCEEDED` and a `Retry-After` header. `locale` remains
> accepted without a validation error for wire compatibility but has no
> effect on this endpoint's 204 no-op behavior. Per ADR-0022 D6, the spam
> honeypot/timestamp challenge is not applied to this authenticated buyer
> action.

### Examples

```curl
curl -X POST "https://api.lynkow.com/storefront/{siteId}/customers/resend-verification" \
  -H "X-Lynkow-Pk: lkw_pk_..." \
  -H "Authorization: Bearer <customer-session-token>" \
  -H "Content-Type: application/json" \
  -d '{ "locale": "en" }'
```

---