Skip to content

Popular

  • Embed not showing on my website
  • Connect Claude or ChatGPT (MCP)
  • Set up a custom domain
  • Order a build through Lumina
  • What Lumina Assistant can do

↑ ↓ to move · Enter to open · Esc to close

Developers

Developer overview

Every way to work with Lumina from code or an AI agent, and which to pick.

Almost everything you can do in the Lumina Sales dashboard, you can also do from code or from an AI agent. Pick the way in that fits the job.

Which one to use

You want to…UseStart here
Do something in your account right now by asking in plain wordsLumina Assistant, inside the dashboardLumina Assistant
Run your agency from Claude Code, Codex, Cursor, Grok Bot, or another AI agentMCP serverMCP server
Connect your own software: a CRM sync, a script, a scheduled jobREST APIAPI quickstart
Put a live demo on a websiteEmbed snippetEmbed install guide
React to demo activity on that website (calls, leads)Embed JavaScript APIEmbed JavaScript API
Publish your Lumina blog posts on your own site automaticallyREST API or webhookPublish blog posts to your site

If you are not a developer, start with Lumina Assistant. If you already use an AI coding tool, connect the MCP server: it is the same API with no code to write.

One API underneath

The MCP server and the REST API are the same thing seen two ways. Every API operation a token can call is also an MCP tool with the same name. Both:

  • live on https://luminasales.io,
  • use the same access tokens,
  • run the same checks as the dashboard: permissions, plan limits, and usage caps.

So anything you can do with curl, your AI agent can do with a tool call, and the other way round.

URL
REST API basehttps://luminasales.io/api/v1
MCP serverhttps://luminasales.io/api/mcp
OpenAPI spechttps://luminasales.io/api/v1/openapi.json
API reference/docs/rest-api
Service status/status

What you can reach

The API covers your agency, branding and custom domains, clients, deals and their portals, client logins and keys, onboarding forms, AI-designed forms and submissions, demos and embeds, landers, analytics and demo leads, fulfillment orders and pricing-call bookings, Scope Calculator estimates, niche and node requests, usage, billing, team, notifications, beta features, referrals, access tokens, and blogs.

A few actions move money, change who has access, or cannot be undone. A token can still ask for them, but each one waits for the owner's approval. See Access tokens.

Access tokens

Both the API and the MCP server take a token that starts with lsk_live_. Only the agency owner can create one, from Developers in the dashboard. A token acts as the person who created it, with that person's permissions. See Access tokens.

Webhooks and notifications

Lumina can tell your systems when something happens:

  • Blog posts. A signed blog.post.ready webhook fires after every new post. Set it up on the Blogs page under Schedule. See Publish blog posts to your site.
  • Slack and Discord. The owner can send events (support requests, revision lists, onboarding submitted, logins handed over, build status, usage alerts, lander leads) to a Slack or Discord channel from Settings → General → Notifications. These are plain chat messages, not signed webhooks.

There are no other outbound webhooks yet. To track changes in other areas, poll the API.

The Lumina Assistant is not an API product

Lumina Assistant runs only inside a signed-in dashboard session. Access tokens cannot start Assistant conversations. If you want an AI to work on your account from outside the dashboard, use the MCP server.

If something goes wrong

Still stuck? Ask Lumina Assistant in your dashboard (⌘J on any page), or read how to get help.