Connect any website to LevelUp
One script line brings SEO, forms, content and booking from your LevelUp dashboard to your website. A small JavaScript API and server keys cover the rest.
Your site ID and keys are on your dashboard's Developers page.
<!-- Before </body>, on every page -->
<script
src="https://levelup-ecosystem.com/sdk/v1/levelup.js"
data-site="ws_your_site_id"
defer
></script>- SEO
- Forms
- Content
- Booking
- Waitlist
Three building blocks, from no code to your own server
Start with the tag. Add the JavaScript API for custom flows, and a server key when your server has something to report.
- No code
The LevelUp tag
One line before
</body>, on any site builder or framework. Everything it does is then managed from your dashboard.- SEO: title, description, social cards and structured data
- Forms sent straight to your LevelUp inbox
- Text and images filled in from your dashboard
- Booking and the waitlist through the JavaScript API
- A few lines
The JavaScript API
The tag exposes
window.LevelUpfor custom forms, booking flows and your own interface.- LevelUp.ready: your site's public content
- submitForm() for contact, quote, newsletter and sign-up forms
- bookAppointment() and joinWaitlist()
- waitlist() and ticketStatus() for walk-in queues
- Server to server
Server keys
Report payments from your server, for example from your Stripe webhook, so your dashboard shows your real revenue.
- Live (
lu_live_…) and test (lu_test_…) keys - Created by owners and admins in the dashboard
- Shown once, stored hashed, revocable at any time
- Live (
Copy, paste, replace the placeholders
ws_your_site_id and lu_live_… are placeholders. Your real site ID and keys are only shown in your dashboard.
- 01
Add the tag
Place it before
</body>on every page, or in your site builder's custom code field, and replacews_your_site_idwith your site ID.data-seo="off",data-forms="off"ordata-analytics="off"on the script tag turns off SEO changes, form handling or page views (no cookie, Do Not Track respected).index.html <!-- Before </body>, on every page --> <script src="https://levelup-ecosystem.com/sdk/v1/levelup.js" data-site="ws_your_site_id" defer ></script> - 02
Connect a form
Add
data-lu-formto any form. The name, email, phone, company and message fields are mapped for you; any other field is kept as extra data. The hidden_hpfield catches bots, anddata-lu-statusshows the result to the visitor.Form types: contact, quote, newsletter, vip_signup and registration.
contact.html <form data-lu-form="contact"> <input name="name" placeholder="Name"> <input name="email" type="email" required> <textarea name="message"></textarea> <!-- Honeypot: keep it hidden and empty --> <input name="_hp" style="display:none" tabindex="-1" autocomplete="off"> <button type="submit">Send</button> <p data-lu-status></p> </form> - 03
Use the JavaScript API
Every method returns a promise. Inputs are checked in the browser and again by the API; when a field is wrong, the error names it.
app.js // The public content of your site, once the tag is loaded. const site = await LevelUp.ready; console.log(site.name, site.features); // contact, quote, newsletter, vip_signup or registration. // Extra fields are kept as data. await LevelUp.submitForm('quote', { name, email, message, budget: '5k' }); // Booking and the walk-in waitlist (when enabled for your site). await LevelUp.bookAppointment({ service: 'haircut', date: '2026-11-12', time: '10:00', name, email }); await LevelUp.joinWaitlist({ name, phone }); // Errors carry err.code (PT403, PT409, PT429...) and err.field. document.addEventListener('levelup:ready', (e) => console.log(e.detail)); - 04
Report payments from your server
Call it from your server only, typically from your Stripe webhook once the signature is verified. The exact endpoint is shown on your dashboard's Developers page once you have an account.
Amounts are integers in minor units (2600 = 26.00). The same event sent twice is ignored, and a paid payment can only move to refunded.
app/api/stripe/webhook/route.ts // Server only: your Stripe webhook, after verifying the signature. // The exact endpoint and public key are on your dashboard Developers page. // LEVELUP_SITE_KEY=lu_live_... is a secret: server environment only. await fetch(process.env.LEVELUP_PAYMENTS_ENDPOINT, { method: 'POST', headers: { apikey: process.env.LEVELUP_PUBLIC_KEY, 'Content-Type': 'application/json' }, body: JSON.stringify({ p_key: process.env.LEVELUP_SITE_KEY, p_event: { provider: 'stripe', provider_event_id: event.id, provider_session_id: session.id, provider_payment_intent: session.payment_intent ?? null, status: 'paid', amount: session.amount_total ?? 0, currency: session.currency ?? 'usd', offer_id: session.metadata?.offer_id ?? null, offer_name: session.metadata?.offer_name ?? null, customer_email: session.customer_details?.email ?? null, customer_name: session.customer_details?.name ?? null, occurred_at: new Date(event.created * 1000).toISOString(), metadata: {} } }) });
The LevelUp API endpoint
The tag talks to one public endpoint for browser calls. You can call it directly with POST and a JSON body.
POSThttps://levelup-ecosystem.com/api/v1/<action>
Every body includes your site ID as "site". Server keys use their own endpoint, shown in your dashboard.
| Action | JavaScript | What it does |
|---|---|---|
| site | LevelUp.ready | Public content of your site: features, settings, services, team, reviews, FAQ |
| website | — | Website, enabled features and public settings only |
| forms | LevelUp.submitForm() | Sends a form to your LevelUp inbox |
| appointments | LevelUp.bookAppointment() | Books an appointment; prices and names come from your dashboard |
| waitlist-join | LevelUp.joinWaitlist() | Joins the walk-in waitlist |
| waitlist | LevelUp.waitlist() | The public waitlist, with names masked |
| tickets | LevelUp.ticketStatus() | Status of a waitlist ticket |
Errors
PT403- Feature not enabled for this website, or a write from a domain that is not registered
PT404- Not found, or the website is not live
PT409- This time slot is no longer available
PT429- Too many requests; try again later
invalid- A field is missing or invalid; its name is returned when known
How your website stays safe, in plain words
The public parts are public on purpose. Everything else stays on your server and in your dashboard.
Public by design
Your site ID and the public key only allow what a visitor can already do: read your published content and send a form, a booking or a waitlist request.
Your domains only
Writes are accepted only from the domains registered for your website. Browsers set the origin of every request, and a web page cannot fake it.
Rate limits
Every write is rate-limited per contact and per website, and every server key has its own limit.
Server keys stay secret
A server key is shown once, stored only as a hash and can be revoked at any time. Creating or revoking one is written to your website's audit log.
Never in the browser
Keep server keys in your server's environment variables. Never put one in browser code, in a public environment variable or in your repository.
Customer data stays private
Submissions, bookings and payments are never readable through the public API. Only members of your organization see them, in the dashboard.
Get your site ID and keys
To get your site ID and keys, create a LevelUp account.
Already have an account? Sign in
01Create your LevelUp account
Use the email address your website is registered with.
02Your website is linked to it
LevelUp sets up each website and links it to its owner. Starting a new project? Tell us about it. Start a project
03Open Developers
After you sign in, you land on your dashboard's Developers page: your site ID, the install line, the install status and, for owners and admins, server keys.
Status and limits
What is available today. This page describes what exists, not plans.
Available now
- LevelUp tag v1: SEO, forms, content, the credit badge and the install check
- JavaScript API: ready, submitForm, bookAppointment, joinWaitlist, waitlist and ticketStatus
- Server keys and payment reporting for Stripe events, in live and test mode
- Booking and the waitlist, on websites where those features are enabled
Limits
- Form submissions: 5 per contact and 300 per website per hour
- Server keys: 300 calls per key every 10 minutes, up to 10 active keys per website
- Requests to the API endpoint: 32 KB of JSON at most
- Link previews on Facebook, WhatsApp and LinkedIn only read your original HTML: when they matter, add the same meta tags on your server
Not available
- Server keys accept payment events only.
- There is no public read access to customer data, by design.