tutorial

Monitoring LemonSqueezy with Vigilmon: Commerce API Uptime, Webhook Health, Checkout Availability & SSL Checks

How to monitor LemonSqueezy commerce platform with Vigilmon — API availability, webhook endpoint health, store checkout uptime, SSL certificate monitoring, and status alerting for 2026.

LemonSqueezy is a commerce platform built for indie developers and SaaS founders — handling digital product sales, subscriptions, licensing, and tax compliance as a merchant of record. When LemonSqueezy has an incident or your integration degrades, customers cannot purchase, license keys cannot be issued, and subscription renewals fail silently. Vigilmon gives you an external monitoring layer over your LemonSqueezy integration: API availability, webhook receiver health, your store's checkout experience, and SSL certificate status on your custom domain.

What You'll Build

  • A monitor on the LemonSqueezy API for external availability tracking
  • A webhook receiver health check confirming your endpoint is ready for LemonSqueezy events
  • A store or product page monitor catching customer-facing issues before they compound
  • SSL certificate monitoring for your custom store domain
  • Alerting tuned for a commerce-critical integration

Prerequisites

  • A LemonSqueezy account with at least one active product or subscription plan
  • A webhook receiver endpoint deployed and publicly reachable
  • A free account at vigilmon.online

Step 1: Monitor the LemonSqueezy API

LemonSqueezy's REST API is used by your backend to retrieve order data, manage subscriptions, fetch license activations, and generate checkout URLs. The API is hosted at api.lemonsqueezy.com:

curl -I https://api.lemonsqueezy.com/v1/products \
  -H "Authorization: Bearer YOUR_API_KEY"

A healthy API returns 200 with a JSON product list. For the Vigilmon check, use a lightweight endpoint that does not require an active API key to confirm reachability:

  1. Log in to Vigilmon → Add Monitor → HTTP.
  2. URL: https://api.lemonsqueezy.com/v1/me (returns 401 without auth — that is the expected response and confirms the API host is up).
  3. Check interval: 60 seconds.
  4. Expected status: 401 (confirms API is reachable and returning proper auth errors).
  5. Label: LemonSqueezy API - Availability.
  6. Click Save.

Why 401 is the target: Sending an unauthenticated request to a protected endpoint returns 401 Unauthorized. This is the correct behavior — it confirms DNS resolves, TLS handshakes succeed, the application server is running, and routing is working. A 502 or 503 means the platform is down.

Step 2: Monitor Your Webhook Receiver

LemonSqueezy sends webhook events for order_created, subscription_created, subscription_cancelled, license_key_created, and more. If your webhook receiver goes down, fulfillment breaks: digital product delivery may fail, license activations stall, and subscription state in your database drifts from LemonSqueezy's records.

Add a monitor on your webhook endpoint:

  1. Add Monitor → HTTP.
  2. URL: https://your-app.example.com/webhooks/lemonsqueezy.
  3. Check interval: 60 seconds.
  4. Expected status: 200 or 405 (GET on a POST-only endpoint returns 405, confirming the route is registered and the app is running).
  5. Label: LemonSqueezy Webhook Receiver.
  6. Click Save.

LemonSqueezy webhook signatures: LemonSqueezy signs webhook payloads with an HMAC-SHA256 signature sent in the X-Signature header. Your receiver should verify this signature before processing. A GET probe returning 405 does not trigger signature validation — it just confirms the endpoint is alive.

Step 3: Monitor Your Store or Product Pages

LemonSqueezy powers your checkout either via hosted checkout pages (on checkout.lemonsqueezy.com) or a custom store URL. Your product pages — where customers first encounter the buy button — must be available and loading correctly. Add a monitor on the page where customers initiate purchases:

curl -I https://your-store.lemonsqueezy.com/
# or your custom domain
curl -I https://your-app.example.com/pricing

Add the monitor:

  1. Add Monitor → HTTP.
  2. URL: https://your-app.example.com/pricing (or your hosted store URL on lemonsqueezy.com).
  3. Check interval: 60 seconds.
  4. Expected status: 200.
  5. Keyword: Buy or a product name (a keyword present in your store page HTML).
  6. Label: LemonSqueezy Store - Pricing Page.
  7. Click Save.

Hosted vs custom domain: If you use LemonSqueezy's hosted store (your-store.lemonsqueezy.com), monitor that URL directly. If you embed checkout on your own site, monitor your site's pricing page and the LemonSqueezy API separately.

Step 4: Monitor SSL Certificates

Expired TLS certificates on your store domain or application domain block purchases entirely. Browsers display full-page certificate warnings that customers interpret as security incidents — they close the tab and do not return.

Add SSL monitoring for your domains:

  1. Add Monitor → SSL Certificate.
  2. Domain: your-app.example.com (your primary domain).
  3. Alert when expiry is within: 30 days.
  4. Alert again: 14 days, 7 days, 3 days, 1 day.
  5. Click Save.

If you use a custom domain on LemonSqueezy (shop.your-app.com), add a second SSL monitor for that domain. Commerce domains need maximum certificate coverage.

Step 5: Track LemonSqueezy's Status Page

LemonSqueezy publishes their system status at status.lemonsqueezy.com. Add a keyword monitor so Vigilmon alerts you the moment LemonSqueezy reports degradation — without requiring you to poll their status page manually during an incident:

  1. Add Monitor → HTTP.
  2. URL: https://status.lemonsqueezy.com/.
  3. Check interval: 5 minutes.
  4. Expected status: 200.
  5. Keyword: All Systems Operational (present during normal operation; absent during incidents).
  6. Label: LemonSqueezy Status Page.
  7. Click Save.

Correlation value: When your API monitor fires and the status page keyword check also fails, the incident is on LemonSqueezy's infrastructure and you can immediately communicate that to your customers. When only your API monitor fires, the issue may be on your end.

Step 6: Configure Alerting

In Vigilmon under Settings → Notifications, set up alert channels for your team:

| Monitor | Trigger | Action | |---|---|---| | LemonSqueezy API - Availability | Non-2xx/4xx or timeout | LemonSqueezy API incident; check status page; pause marketing sends | | LemonSqueezy Webhook Receiver | Non-200/405 or timeout | App server down; orders will queue in LemonSqueezy; fix app server | | LemonSqueezy Store - Pricing Page | Non-200 or keyword missing | Checkout page broken; new purchases blocked; investigate app deployment | | LemonSqueezy Status Page | Keyword missing | Platform incident; communicate to customers; pause paid campaigns | | SSL Certificate | < 30 days to expiry | Renew certificate; store will become inaccessible without valid cert |

Alert sensitivity: Configure all commerce monitors to alert after 1 consecutive failure. The cost of a false alarm (a quick Slack message) is trivially smaller than a missed payment outage.

Common LemonSqueezy Failure Modes and What Vigilmon Catches

| Scenario | Vigilmon monitor | |---|---| | LemonSqueezy API incident | API Availability fires; Status Page keyword fails | | Webhook receiver app server crash | Webhook Receiver fires; unfulfilled orders accumulate | | Failed deploy breaks pricing page | Store Pricing Page fires with unexpected status | | SSL certificate expires on custom domain | SSL monitor alerts at 30-day threshold | | LemonSqueezy checkout.lemonsqueezy.com outage | API monitor fires; Status Page keyword fails | | Application memory leak causes OOM crash | Webhook Receiver and Pricing Page fire simultaneously | | DNS misconfiguration on custom store domain | Pricing Page fires with DNS resolution error | | Database unavailable to your webhook handler | Webhook Receiver returns 500; orders not fulfilled | | LemonSqueezy scheduled maintenance | Status Page keyword may fail; API monitor may fire |

Why Monitor LemonSqueezy with an External Tool

LemonSqueezy's own status page tells you about LemonSqueezy's infrastructure. Your application logs tell you about errors your code catches. But neither tells you about the silent failure modes: a webhook receiver that returns 200 for GET but panics on POST, a checkout page that loads but fails to initialize lemonsqueezy.js, or an SSL certificate expiring on a subdomain that nobody is watching. Vigilmon monitors the complete chain — from DNS to TLS handshake to HTTP response to content verification — from outside your infrastructure, with no dependency on your application being healthy.

For indie developers and small SaaS teams, commerce downtime is not an abstract metric. It is revenue that does not arrive.

LemonSqueezy removes the complexity of global digital commerce and tax compliance. Vigilmon removes the uncertainty of whether your commerce integration is available right now.

Start monitoring your LemonSqueezy integration in under 5 minutes — register free at vigilmon.online.

Monitor your app with Vigilmon

Free plan — 5 monitors, no credit card required. Up and running in 60 seconds.

Start free →
← Back to all articles