Introduction

curl -X POST https://your-domain.com/api/v1/subscribe \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ll_live_your_key_here" \
  -d '{"email": "user@example.com"}'

ll_live_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6

fetch('/api/v1/subscribe', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer ll_live_your_key_here'
  },
  body: JSON.stringify({ email: 'user@example.com' })
})

fetch('/api/v1/subscribe', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-API-Key': 'll_live_your_key_here'
  },
  body: JSON.stringify({ email: 'user@example.com' })
})

{
  "email": "user@example.com",
  "name": "Jane Smith"
}

const res = await fetch('https://your-domain.com/api/v1/subscribe', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer ' + process.env.LAUNCHLIST_API_KEY
  },
  body: JSON.stringify({ email, name })
})

const data = await res.json()
if (res.status === 201) console.log('Subscribed!')
else if (res.status === 200) console.log('Already on the list')
else console.error(data.error)

import requests, os

res = requests.post(
    'https://your-domain.com/api/v1/subscribe',
    headers={
        'Authorization': f"Bearer {os.environ['LAUNCHLIST_API_KEY']}"
    },
    json={'email': 'user@example.com', 'name': 'Jane Smith'}
)

print(res.json())

curl -X POST https://your-domain.com/api/v1/subscribe \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $LAUNCHLIST_API_KEY" \
  -d '{"email": "user@example.com", "name": "Jane Smith"}'

$ch = curl_init('https://your-domain.com/api/v1/subscribe');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_POST           => true,
    CURLOPT_HTTPHEADER     => [
        'Content-Type: application/json',
        'Authorization: Bearer ' . getenv('LAUNCHLIST_API_KEY'),
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'email' => 'user@example.com',
        'name'  => 'Jane Smith',
    ]),
]);
$res = json_decode(curl_exec($ch), true);
curl_close($ch);

// Custom widget calling the public endpoint
const res = await fetch('/api/v1/widget/my-saas-beta', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ email: 'user@example.com' })
})

<!-- Place where you want the widget to appear -->
<div id="ll-widget-your-slug"></div>
<script>
(function(){
  var i = document.createElement('iframe');
  i.src = 'https://your-domain.com/embed/your-slug';
  i.style.cssText = 'width:100%;height:0;border:none;display:block;';
  i.setAttribute('scrolling', 'no');
  var el = document.getElementById('ll-widget-your-slug');
  if (el) el.appendChild(i);
  window.addEventListener('message', function(e) {
    if (e.data && e.data.ll_slug === 'your-slug')
      i.style.height = e.data.ll_height + 'px';
  });
})();
</script>

<iframe
  src="https://your-domain.com/embed/your-slug"
  style="width:100%;border:none;min-height:280px;"
  frameborder="0"
  scrolling="no"
></iframe>

Is there a rate limit on the subscribe endpoint?

The API key endpoint has no hard rate limit in the current version. The widget endpoint (no auth) has basic protection against abuse at the infrastructure level. Both will gain configurable rate limits in a future release.

Can I export my subscribers?

Yes — open a project in the dashboard, view the subscribers table, and export functionality is coming soon. In the meantime, you can query the subscribers table directly from your Launchlist dashboard.

Will a subscriber see an error if they submit twice?

No. The subscribe endpoint is intentionally idempotent — a duplicate email returns 200 OK with the message "Already subscribed" rather than an error. This lets you safely call the endpoint without de-duplicating on the client.

Does the widget work inside a React app?

Yes. Use the script embed or iframe — both work in React, Next.js, or any framework. Alternatively, call /api/v1/widget/[slug] directly from your own form component.

Is the embed CORS-friendly?

Yes. Both subscribe endpoints include Access-Control-Allow-Origin: * headers so they can be called from any domain.

What data is stored per subscriber?

email, name (optional), source (api or widget), and created_at. You can pass extra metadata via the metadata field in direct database inserts.

How do I delete a subscriber?

A subscriber management UI with delete support is on the roadmap.