Introduction
Show our Leads, pixel install and other screens inside your own app, under your brand, in an iframe.
Your menu on the left, our Leads and pixel-install screens on the right, in an iframe. Your users sign in to your app only, your server opens each session, and nothing secret ever reaches the browser. Most teams are live in a day.
Try it
This is exactly what your users see (our read-only demo account; pixel checks are simulated, so any domain works).
No domain yet, so the field is open. Type any domain and click Verify: the check fails and the screen explains what to fix.
Three ways to integrate
Not sure embedded screens are the right fit? Compare them:
| API only | Embedded screens | Full white label | |
|---|---|---|---|
| Where your clients work | Your own screens, fed by our API | Your app, with our screens in an iframe | Our dashboard on your domain (reveal.yourdomain.com) |
| Who signs them in | You | You (we never see their password) | Our sign-in page, with your brand |
| What you build | The leads list, pixel install, settings | One server endpoint and an iframe | Your marketing site and your billing |
| Who bills your clients | You | You | You: your server calls our API on every payment |
| Time to launch | Weeks | A day | A few days (DNS + branding) |
All three use the same building blocks: one website per client, created with your master key, and leads (credits) that follow what the client pays you.
Your path through this section
1. Quickstart
Your own website inside a local page in about 10 minutes: one key, one call, one HTML file.
2. Understand the flows
One-time setup, a client signing up, a client logging in: every call in order, as a diagram and as API calls.
3. Build it, step by step
Your domain and keys, what your users see, a website per client, the one-time link, the iframe.
4. Billing
Leads follow what your clients pay you: trial, paid, plan change, cancel.
5. Go live
Bring your existing clients across, run the security checklist, or let your AI assistant build it.
The two keys
| Key | Looks like | Where you get it | What it can do |
|---|---|---|---|
Master key (HL_MASTER_KEY) | master-priv-… | Account settings → API Keys | Create and change websites, set credits and trials. Sent as ?privateKey=. |
Embed key (HL_EMBED_KEY) | hle_… | Account settings → White label → Embed in your app | Only open embedded sessions. Sent as Authorization: Bearer. |
Both keys stay on your server
Never put either key in front-end code, a mobile app or a public repository. The browser only ever gets a link that works once.