Skip to Content
SendlySendly

Send a test email with no account

Try Sendly with no signup and no API key: confirm your email with a 6-digit code, send 20 free test emails to your own inbox, and claim the test project into a free account later.

You can try Sendly before you make an account. One call with your email address starts a keyless test project: Sendly emails you a 6-digit code, and once you confirm it you can send 20 free test emails to that inbox. No signup, no domain, no DNS and no card. When you want more, claim the project into a free account and everything you sent comes with it.

This page is written for both people and coding agents. An agent can run every step itself; the only thing it needs from you is the code from your inbox.

1. Start

curl -X POST https://api.sendly.now/api/v1/keyless/start \
  -H "Content-Type: application/json" \
  -d '{ "email": "you@yourcompany.com" }'

Starting a keyless project costs a small proof of work, so the first call answers 428 with a challenge:

{
  "status": 428,
  "code": "proof_required",
  "details": {
    "reason": "proof_missing",
    "challenge": "AQAUAAABmp…",
    "algorithm": "sha256",
    "difficultyBits": 20,
    "expiresAt": "2026-11-17T09:05:00.000Z",
    "header": "Sendly-Keyless-Proof",
    "howTo": { "node": "node -e \"…\"", "python": "python3 -c \"…\"", "pythonWindows": "py -c \"…\"" },
    "signUpUrl": "https://app.sendly.now/auth/signup"
  }
}

Find a decimal nonce (at most 32 digits) such that SHA-256 over the UTF-8 bytes of <challenge>:<nonce> starts with difficultyBits zero bits. details.howTo.node and details.howTo.python are ready-to-run one-liners with your challenge filled in; each prints the full header value. On Windows use details.howTo.pythonWindows (the py launcher), since stock Windows has no python3. At the usual 20 bits that takes 1 to 3 seconds. The same solver, standalone:

# CHALLENGE and BITS come from details.challenge and details.difficultyBits.
PROOF=$(node -e "const c=process.argv[1],d=+process.argv[2],k=require('crypto'),h=(s)=>k.createHash('sha256').update(s).digest('hex');for(let n=0;;n++)if(parseInt(h(c+':'+n).slice(0,8),16)>>>(32-d)===0){process.stdout.write(c+':'+n);break}" "$CHALLENGE" "$BITS")

Send the same request again with the proof:

curl -X POST https://api.sendly.now/api/v1/keyless/start \
  -H "Content-Type: application/json" \
  -H "Sendly-Keyless-Proof: $PROOF" \
  -d '{ "email": "you@yourcompany.com" }'
{
  "key": "pk_test_…",
  "project_id": "5f0c…",
  "email": "you@yourcompany.com",
  "verified": false,
  "code_expires_at": "2026-11-17T09:20:00.000Z",
  "test_allowance": { "limit": 20, "used": 0, "remaining": 20 },
  "claim_url": "https://app.sendly.now/claim/keyless#pk_test_…",
  "next": { "call": "POST /api/v1/keyless/verify", "say": "I sent a 6-digit code to you@yourcompany.com. Tell me the code… check your Spam folder." }
}

Keep the key. It is shown once. It is a test key: it can only send test emails to the address you confirm, and every other endpoint refuses it.

Each challenge works once and for 5 minutes. You are only asked for a proof when the call would otherwise succeed: a bad email or a spent limit answers its own error first.

2. Confirm your email

Sendly sends a 6-digit code to the address you gave. Paste it back (an agent asks you for it):

curl -X POST https://api.sendly.now/api/v1/keyless/verify \
  -H "Authorization: Bearer pk_test_…" \
  -H "Content-Type: application/json" \
  -d '{ "code": "123456" }'

A code lasts 15 minutes and allows 5 tries. No email? Check your Spam folder first, then GET /api/v1/keyless with the same key: its code_email.status says whether the code email is queued, sent, delivered, bounced, unconfirmed (our mail provider never answered, so it may still arrive) or not_sent, and code_email.say is a sentence for your user. POST /api/v1/keyless/resend sends a new code (up to 3 codes, a minute apart); a code whose email Sendly could not send (not_sent) does not count against the 3, up to 5 such resends. A resend Sendly cannot send at all answers 503 and does not count either. The reply's next.say tells your user how many test emails are left.

3. Send your test emails

curl -X POST https://api.sendly.now/api/v1/emails/test \
  -H "Authorization: Bearer pk_test_…" \
  -H "Content-Type: application/json" \
  -d '{ "subject": "Hello from Sendly", "body": "<p>It works.</p>" }'

The email comes from your project's sandbox address (test-…@sendly.now) and can only reach the address you confirmed. A first email from a new sender can land in Spam: if it is not in the inbox within a minute, look there. The response's test_allowance counts down from 20. GET /api/v1/keyless with the same key shows where you stand.

4. Claim it when you want more

Open claim_url and sign up for free (or sign in). If you sign up with an email and password, the confirmation link can open in a new tab: the claim page there carries on, and so does the first tab once your address is confirmed. The pk_test_ key stops working once the project is claimed: use your account's API keys from then on. The test project moves into your account with everything it sent, and you can add your own domain, which sends to anyone. The free plan needs no card; see pricing. The 20 test emails are per project, so claiming does not reset them.

Limits

  • 20 test emails per keyless project, only to the confirmed address.
  • Keyless projects are for testing: an unconfirmed one is deleted after 24 hours, an unclaimed one after 30 days. Claim it to keep it.
  • One inbox can start 3 keyless projects a day (plus-aliases like you+1@ count as that inbox), and one network (an IPv4 /24 or IPv6 /48) 5 a day. These counts reset at 00:00 UTC: a 429 says so in its detail, and details.resetsAt is the exact time. A start whose code email Sendly could not send (code_email.status is not_sent because of a problem on our side) does not count: the next start from that inbox or network gives its place back. A start answered 503 because the code could not be sent at all does not count either.
  • An agent that cannot run code can skip the proof of work with a free account instead (details.signUpUrl), or connect over MCP and call send_test_email.

On this page