Request newsletter confirmation
Requests double opt-in confirmation for the submitted email and optional profile. The endpoint accepts anonymous requests. An optional Cognito JWT or Aura Historia access-token bearer credential may be supplied; an invalid supplied credential returns 401. For an authenticated user, omitted profile values can fall back to that user's stored profile, but the credential never proves ownership of the submitted mailbox and never skips confirmation, including when the submitted address exactly matches the caller's account email.
The body is limited to 8 KiB. Every result is Cache-Control: no-store. Empty 204 means the request was handled, including when rate suppression applies. It does not reveal account or pending-challenge state, confirm a subscription, or mean that email was delivered or Loops was called. Loops synchronization occurs asynchronously after confirmation.
Request
- Base URL: https://api.stage.aura-historia.com
- URL: https://api.stage.aura-historia.com/api/v1/newsletter-subscriptions
- Auth: one of:
- HTTP bearer
- none
Request body
Example request
{
"email": "collector@example.com",
"firstName": "Ada",
"lastName": "Lovelace",
"language": "de",
"currency": "EUR"
}Response
Confirmation request handled. The requested mailbox may be pending, already confirmed, or rate suppressed.