DocsLiulum Care · Headless Commerce Guide

Monitor any headless storefront.

No SDK to install. No agent to deploy. Add your URLs and Care starts watching your API routes, checkout flow, and edge functions immediately.

Next.js

App Router and Pages Router

Nuxt

v3 and v4

Remix

Any deployment target

SvelteKit

Vercel, Netlify, Node

Astro

SSR and static

Custom stack

Any publicly reachable URL

01 / Step

Add your store to Care

In the Liulum dashboard, go to Portfolio and click Add site. Paste your storefront URL (e.g. https://your-store.com). Care will immediately start probing uptime and SSL.

02 / Step

Configure critical paths

In Site Settings, add the URLs that matter most for revenue: your product page, cart API route, and checkout endpoint. Care monitors these with full HTTP assertion — not just a ping.

# Example critical paths to add
https://your-store.com/               # Homepage
https://your-store.com/products/[slug] # Product page
https://your-store.com/api/cart        # Cart API
https://your-store.com/checkout        # Checkout flow

03 / Step

Set expected responses

For each path, tell Care what a healthy response looks like — status code, response time threshold, and an optional body assertion (e.g. check that the JSON contains a cart object). This prevents false positives from redirects or maintenance pages.

# Example assertion config (set in dashboard)
path:     /api/cart
method:   POST
status:   200
max_ms:   1500
contains: \"cart\"

04 / Step

Connect your alert channel

In Settings > Alerts, add your Slack channel, email, or webhook URL. Care will notify you the moment a monitored path fails, with a plain-English summary of what broke and what it returned.

05 / Step

Connect guarded recovery (optional)

For eligible managed stores, connect scoped hosting access and pre-approve only the playbooks shown for that provider. A recovery runs only when the purchased plan, project policy, failure match, and confidence threshold all allow it.

06 / Step

Add the trust badge

Copy the snippet below into your store footer. The badge updates live with your store health grade — a trust signal for customers and proof of active monitoring.

<a href="https://liulum.com" target="_blank" rel="noopener">
  <img
    src="https://liulum.com/api/public/badge/YOUR-PROJECT-ID.svg"
    alt="Protected by Liulum Care"
    height="32"
  />
</a>

Troubleshooting

Common setup issues

Care reports a 301 or 302 for my URL
Use the final destination URL after all redirects. Care does not follow redirects by default — this prevents false-positive green status on pages that silently redirect to maintenance modes.
My API route requires authentication
For private API routes, use a dedicated health endpoint that returns 200 without credentials. Never pass API keys to Care — monitor only public-facing or purpose-built health check URLs.
I see high latency alerts but the site feels fast
Cold-start latency on serverless or edge functions can spike on first request. Set your latency threshold in Site Settings to account for your expected warm vs cold p95 response times.
The badge shows degraded even though the site is up
Care monitors all configured paths, not just the homepage. Check Portfolio > your site > Incidents to see which specific endpoint triggered the degraded status.

Ready to start monitoring?

Add your headless storefront to Liulum Care in under 5 minutes.

Start Care Why headless needs Care →

# Example critical paths to add https://your-store.com/ # Homepage https://your-store.com/products/[slug] # Product page https://your-store.com/api/cart # Cart API https://your-store.com/checkout # Checkout flow

Common setup issues

Care reports a 301 or 302 for my URL

Use the final destination URL after all redirects. Care does not follow redirects by default — this prevents false-positive green status on pages that silently redirect to maintenance modes.

My API route requires authentication

For private API routes, use a dedicated health endpoint that returns 200 without credentials. Never pass API keys to Care — monitor only public-facing or purpose-built health check URLs.

I see high latency alerts but the site feels fast

Cold-start latency on serverless or edge functions can spike on first request. Set your latency threshold in Site Settings to account for your expected warm vs cold p95 response times.

The badge shows degraded even though the site is up

Care monitors all configured paths, not just the homepage. Check Portfolio > your site > Incidents to see which specific endpoint triggered the degraded status.