Choose one application event
Start with a completed event such as signup or order confirmation. Define what the message must tell the recipient and what action comes next. Keep verification emails focused on account access; do not mix unrelated promotions into a message someone needs to complete a task.
Keep sending credentials on the server
Follow the current Woyra API documentation to create credentials and authenticate your sending domain. Store credentials in server-side configuration, never browser code or a public repository. Use the documented request format and check API errors explicitly. Send a small test message before connecting a production workflow.
Make retries safe
Use a stable idempotency key for the same application event so a retry can be recognized. Separate a new event from a repeated request. Design a clear response for temporary failure and for a permanently rejected address. Avoid retrying indefinitely or repeatedly mailing an address after a hard bounce.
Measure what happened after acceptance
Record the API response separately from later delivery events. API acceptance is not proof of inbox placement. Follow the current documentation for webhook verification and event handling, and make event processing tolerant of duplicates. Test valid addresses, invalid addresses, suppression and recipient replies before increasing traffic.