Email Gun.

API Keys

Partial

Create `eg_...` sending keys in the dashboard portal (not via Swagger).

Generate a sending key in the portal

Programmatic send (OTP, transactional, bulk, campaigns) uses an API key (eg_...), not a dashboard login token.

  1. Sign in at the Email Gun dashboard
  2. Open API keys
  3. Create a key and copy it immediately (shown once)
  4. Store it on your server (environment variable). Never put it in the browser, localStorage, or a public repo.

Then call send endpoints with:

  • Authorization: Bearer eg_... or
  • X-API-Key: eg_...

Do not use a dashboard JWT/access token for sending.

Interactive API docs: https://email-gun-api.quecko.org/docs

Security notes

  • The plaintext key is shown only once at create time.
  • In production, keep AUTH_REQUIRED=true / API_KEY_REQUIRED=true so sending is never anonymous.
  • Revoke unused keys from the same API keys page.

Related guides

OTP (Transactional Code Emails)

Fast, rate-limited OTP delivery via API keys + templates.

Sending Emails

OTP, transactional email, and campaign broadcasts that deliver.