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.

      Shared and dedicated IPs

      Today: everyone is shared

      Every workspace sends from the same IP address. There is no per-workspace routing in the send path, so nothing you configure changes where your mail appears to come from.

      What the request endpoint does

      You can register interest, and that is genuinely all it does:

      curl -X POST https://api.lockally.com/v1/dedicated-ip-requests \
        -H "Authorization: Bearer $LOCKALLY_API_KEY" \
        -H "Content-Type: application/json" \
        -d '{"note":"Sending 200k/month from a verified domain, want to isolate reputation."}'
      curl -s https://api.lockally.com/v1/dedicated-ip-requests \
        -H "Authorization: Bearer $LOCKALLY_API_KEY"

      It files a request for a human to read and resolve, which is the whole mechanism: provisioning and warm-up are scoped with you rather than handed over automatically. It does not reserve an address and does not change your sending until that conversation happens. Needs tenant:admin to create and tenant:read to list.

      GET /v1/ip-assignment reports which pool your workspace is attached to. It is bookkeeping: the answer is the default shared pool, and the send path does not consult it.

      Why you probably do not want one

      This is worth saying plainly, because dedicated IPs are widely assumed to be the premium option and for most senders they are worse.

      A dedicated IP starts with no reputation at all. You give up an established shared IP for a cold one, and you then have to warm it yourself. The first weeks are measurably worse than staying put.

      It needs volume to stay warm. The usual working figure is a consistent tens of thousands of messages a month, every month. Below that, providers see an address that sends rarely, which reads as less trustworthy rather than more. Intermittent sending from a dedicated IP is the worst of both worlds.

      You absorb your own mistakes with no buffer. On a shared IP a bad campaign is diluted. On a dedicated one it is the whole signal.

      Domain reputation increasingly matters more. Providers weight the authenticated sending domain heavily, and that is already yours. See Domain reputation.

      When a dedicated IP is the right answer

      • Sustained high volume, consistently, month after month.
      • A genuine need to isolate your reputation from other senders, usually compliance-driven or because you send at a scale where you are the pool.
      • A requirement to present a fixed, allowlistable sending address to a recipient organisation.

      If one of those is you, file a request with the volume and the reason in the note. That is the information needed to have the conversation.

      What to do in the meantime

      The things that would make a dedicated IP work are the same things that make the shared IP work for you, and they pay off immediately either way:

      1. Authenticate properly and align DMARC.
      2. Keep the bounce rate low and the list clean.
      3. Build a steady volume curve rather than spikes.
      4. Separate your bulk and transactional sending so one cannot poison the other’s reputation at the domain level, using subdomains. See Domain reputation.