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.

      IP and domain warm-up

      A brand new sending identity that emits fifty thousand messages on its first day looks exactly like a compromised one. Warm-up is the ramp that stops that happening, and here it is enforced rather than advised.

      The schedule

      One schedule, used by both caps below. It roughly doubles every few days and ends after 30 days.

      Days Messages per day
      1 to 2 50
      3 to 4 100
      5 to 7 500
      8 to 10 1,000
      11 to 14 2,500
      15 to 18 5,000
      19 to 22 10,000
      23 to 26 25,000
      27 to 30 50,000
      31 onward no cap

      Days are UTC, and the counter resets at UTC midnight. Test-key sends are not counted.

      Two caps, counted differently

      Domain warm-up applies to a newly verified domain and counts only mail from that domain. It starts when the domain begins warming; a domain that predates the feature has no start date and is treated as warm.

      Pool warm-up applies to the shared sending IP and counts every message from every workspace on the platform. Reputation accrues to the IP, so the ramp has to be measured at the IP.

      Both use the table above, independently. Whichever bites first is the one you hit.

      Hitting the cap

      {
        "status": 429,
        "title": "Domain warm-up cap reached",
        "detail": "news.example.com is warming up: capped at 500 messages/day (day 6 of the ramp). Resets at UTC midnight."
      }

      The response carries Retry-After set to the seconds remaining until UTC midnight, so a client that honours it waits exactly the right amount rather than hammering. The pool-wide version is titled Warm-up cap reached and says “the platform is capped”.

      Neither is a failure of your request. The message was not sent and nothing was consumed.

      Knowing where you are

      While the pool cap is active, successful sends carry headers:

      X-Warmup-Day: 12
      X-Warmup-Daily-Cap: 2500
      X-Warmup-Used-Today: 1840

      There are no equivalent headers for domain warm-up. Ask the domain instead:

      curl -s https://api.lockally.com/v1/domains/$DOMAIN/detail \
        -H "Authorization: Bearer $LOCKALLY_API_KEY"

      It reports domain_warmup_active, domain_warmup_day, domain_warmup_daily_cap and domain_warmup_used_today, which is everything you need to pace a send without waiting to be refused. Scope domains:read. The console’s domain page shows the same figures.

      Working with it rather than against it

      Plan the first month. If a launch needs 40,000 messages, the schedule does not permit that until around day 27. Either start the domain warming well before the launch, or stage the launch across days.

      Spread across the day. The cap is daily, so a client that sends its whole allowance in the first minute spends the rest of the day rejected. Pace it.

      Send your best mail first. The ramp is about building evidence, and the evidence is the engagement of what you send during it. Warming a domain with your least engaged segment wastes the window.

      Do not warm with mail nobody asked for. Volume during warm-up with a high bounce rate is worse than no warm-up at all, and the reputation engine still applies throughout.

      What there is not

      Warm-up is readable but not controllable: there is no way to start, pause, skip or accelerate it. It begins when a domain is verified and runs the fixed schedule above. If you need it changed, that is a support conversation.