Prepare a SendHog sending domain and key

SendHog manages the sending infrastructure; its quickstart does not require you to operate an AWS account or request SES production access yourself. Domain verification and account limits still apply.

Set up the application identity

1. Add a domain you own in the SendHog dashboard.
2. Publish that domain’s generated authentication records. Do not copy the record values from a marketing screenshot or another customer’s example.
3. Run Check DNS and wait for verification before testing mail. Preserve MX records serving your existing employee inboxes.
4. Create a sending key with email.send permission and store it server-side. The full key is shown when created; do not put it in frontend configuration.

Record the sender/domain allowed by this credential. Reading message state or managing webhooks requires additional permissions; sending access alone is not an administration token.

Verify the correct layer

Check the dashboard’s verified state, then send a single approved message using the next guide. If DNS is pending, confirm the authoritative provider’s record names and values rather than starting an unrelated AWS setup.

SendHog credentials belong to SendHog. Its provider-style SDK interfaces are compatibility surfaces, not permission to call an existing AWS, Postmark, or Resend account with the same token.

Source: SendHog quickstart. Account approval, limits, and supported SDK installation details must be checked against the current service documentation.