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.

      Consent and unsubscribes

      The distinction that decides everything

      Transactional Bulk or marketing
      What it is a response to something the person did something you decided to send
      Examples receipt, password reset, OTP, shipping update newsletter, offer, announcement
      Consent implied by the transaction required, and you must be able to show it
      Unsubscribe not required required
      Stream on the platform transactional broadcast

      The platform decides the stream from one field. "unsubscribe": true on a send marks it bulk, puts it in the broadcast stream, and adds the one-click headers. Everything else is transactional.

      That single flag is also the honesty check: if you are reluctant to set it because you do not want the unsubscribe link, the message is marketing and the reluctance is the answer.

      What the platform does for you

      Set "unsubscribe": true and we add RFC 8058 one-click headers: List-Unsubscribe and List-Unsubscribe-Post. Gmail and Yahoo require those for bulk senders, and a reader clicking the provider’s own unsubscribe control is suppressed without your code running at all.

      See Unsubscribe management for the mechanics, including what you still have to put in the body yourself.

      What the platform cannot do for you

      It cannot hold your consent records. There is no consent field, no double-opt-in flow and no proof-of-consent store. Where the person agreed, when, and to what, lives in your system, and it is what you will be asked for.

      It cannot tell a purchased list from an earned one. It will send to both, and the bounce and complaint rates that follow will reach your reputation and then your rate cap. The platform’s protection is after the fact, not before.

      It cannot decide whether a message is transactional. That flag is yours.

      Suppression is a compliance control, not a convenience

      An address lands on the suppression list from a hard bounce, a complaint, an unsubscribe, or a manual entry. Suppressed addresses are filtered out of sends before anything is queued.

      The reason matters, because the filtering differs:

      Reason Blocks
      complaint, bounce every send, including transactional
      unsubscribe, manual opt-in sends only

      So a person who unsubscribed from your newsletter still receives their password reset, and a person who marked you as spam receives nothing at all. That second one is deliberate: a complaint is the strongest signal a recipient can give, and honouring it only for marketing would be honouring it barely.

      Before a first campaign

      Bulk sending on a domain with no history is the most common way to damage a domain that has never done anything wrong. Warm-up caps exist and are visible on the domain detail. See IP and domain warm-up.