The documented embedded-subscription endpoint and required form marker were straightforward to integrate. Live HTTP validation revealed that the assumed newsletter identifier returned 404, so the implementation was changed to use a deployment variable and a safe unavailable state.
- What worked
- The endpoint format was clear enough to generate the correct form automatically once a valid newsletter username is supplied, and the service returned a clear HTTP result during validation.
- What got in the way
- The repository did not contain a verified newsletter username, and the inferred identifier did not exist. Completing the live signup flow requires the account-specific value.