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.

      Rejected sends

      Three different things refuse a send and they are easy to confuse, because all three happen before anything is queued and two of them return 403.

      Sender not authorised

      { "status": 403, "title": "Sender not authorised", "detail": "..." }

      The from address is not one this workspace may send as. The rule depends on the account’s mode:

      Mode What qualifies
      api any address on a domain you have verified
      business, both a mailbox you hold, or an alias on a verified domain

      Verification is per exact domain. Subdomains do not inherit: verifying example.com does not authorise mail.example.com, because each is proved separately.

      A catch-all grants no sending rights. It creates no alias rows, and the rule reads aliases.

      Domain not verified

      The same refusal from the other side. If GET /v1/domains/{domain}/detail shows the domain unverified, no address on it can send on a live key.

      A domain can also be not registered at all, which is a different state and is reported separately: not_registered on the domain list and detail, with a badge in the console, for the case where somebody added a domain nobody has bought. No amount of DNS work fixes that one, because there is no zone to put records in. See DNS troubleshooting.

      Message rejected

      Not a 403. The send was authorised and then stopped by a policy:

      Every recipient suppressed. Returns 200, not an error, with "status": "suppressed" and a warning. It is a success no-op rather than something to retry, and it is the one case where the status code changes rather than the body. Check GET /v1/suppressions for the address.

      Data Loss Prevention. 422 Blocked by Data Loss Prevention. If your workspace enforces DLP, a message carrying something that matches a rule is refused. This runs before the test-mode divert, so a test send is refused too, which surprises people whose fixture data contains card-shaped numbers.

      Reply loop detected. 429, from the agent surfaces, when a reply would continue a loop the platform can see.

      Telling them apart

      You see It is
      403 Sender not authorised the from address, on a live key
      200 with "status": "suppressed" every recipient was on your suppression list
      202 with "status": "delivered" and a test message id a test key, working normally
      422 Blocked by Data Loss Prevention the content, not the sender
      429 Reply loop detected an agent reply the platform stopped

      After acceptance

      A 202 is acceptance into the queue, not delivery. If the send was accepted and nothing arrived, that is a different investigation: Debugging a failed request, then Temporary and permanent failures.