Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Safe production testing

      Everything a test key can prove, it proves better, because it runs the production path. But three things it cannot prove, and all three matter:

      • that mail arrives
      • that it arrives in the inbox rather than the spam folder
      • that it looks right in a real client

      Those need a live send. This page is about running them without touching a customer.

      Send to yourself, on a domain you own

      The whole of safe production testing is choosing the recipient.

      Use an address you control on a domain you own, ideally a catch-all so each check can use a fresh address with no mailbox to create. Never use a customer address, a scraped address, or an address you are not certain is yours, because a live send to a wrong address is a real delivery with a real reputation cost and possibly a real complaint.

      A release check worth running

      1. Send one live message through the code path you changed, to your own address, with a subject that identifies the build.

      2. Read status and message_id. queued is expected here, unlike a test send. Keep the id.

      3. Confirm it arrived, and where. Inbox or spam is the result you cannot get any other way.

      4. Check it rendered. Open it on a phone as well. The template preview and the stored test-key body both show you the HTML; neither shows you what a client does with it.

      5. Check the recorded outcome against what you observed:

        curl -sS "https://api.lockally.com/v1/messages?limit=5" \
          -H "Authorization: Bearer $LOCKALLY_LIVE_KEY"

        A delivered that is sitting in your spam folder is the single most useful discrepancy this check produces. Delivery means the receiving server accepted it, never that a human will see it.

      6. Check your own reputation before and after anything at volume:

        curl -sS https://api.lockally.com/v1/reputation \
          -H "Authorization: Bearer $LOCKALLY_LIVE_KEY"

        Scope send:read. It reports healthy or throttled, the measured bounce rate, the current rate cap and the thresholds acted on.

      Before a first real campaign

      A new domain ramps. Sending a day’s worth of mail on day one is the most common way to damage a domain that has never done anything wrong. The caps are visible on GET /v1/domains/{domain}/detail as domain_warmup_active, domain_warmup_day, domain_warmup_daily_cap and domain_warmup_used_today. See IP and domain warm-up.

      What not to do

      Do not test against your own suppression list. Deliberately bouncing a real address to see the suppression land leaves it suppressed, and suppression exists precisely so that does not get undone casually.

      Do not use a live key in CI. Not because something will go wrong once, but because the day somebody parameterises the recipient from a fixture, it sends to whatever the fixture says.

      Do not disable webhook signature verification to get a test through. The one place that switch is tempting is also the one place it is dangerous.