Site Creation API

The Site Creation API queues a full website build for one business and lets you check on it until it finishes. It uses the same API keys and the same credit balance as the Lead Gen API.

Base URL

Send requests to the same domain you use for your dashboard. Every path on this page is relative to it.

Authentication

Send your API key as a bearer token on every request:

Authorization: Bearer YOUR_API_KEY

Keys start with lgen_. To create one, open API Keys in your dashboard, type a name in the Key label box (up to 64 characters), and click + Create New Key. The full key is shown once, in the Your new API key window. Copy it before you click Done. If you lose it, revoke it and create a new one.

A missing, unknown or revoked key gets 401 with "Missing or invalid bearer API key."

Create a site

POST /api/provision

A valid request queues the build, uses 1 site credit, and returns 202. You need at least 1 credit on your account.

Required fields

Optional fields

Accepted but not applied yet

These fields pass validation, but the build does not act on them. Each one adds a line to warnings when it has an effect you might expect.

• createServicePages, createServiceAreaPages, createLocationPages (booleans, default true). Sending false does not stop those pages from being created.
• locations (list). Only the main address is used.
• googlePlaceId (string). Ignored.

Example request

curl -X POST "https://YOUR_DOMAIN/api/provision" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "businessName": "Example Plumbing",
    "industry": "Plumbing",
    "email": "[email protected]",
    "phone": "(555) 010-0100",
    "address": "100 Main St, Springfield, IL 62701",
    "aboutBusiness": "Example Plumbing repairs and installs residential plumbing.",
    "services": ["Drain cleaning", "Water heater installation", "Leak repair"],
    "serviceAreas": ["Springfield", "Riverton", "Chatham"],
    "look": "classic",
    "primaryColor": "#2F6B55",
    "backgroundTheme": "light"
  }'

Response

Status 202:

{
  "slug": "example-plumbing",
  "siteId": "3f2a9c1e-5b7d-4e8a-9c0f-1a2b3c4d5e6f",
  "previewUrl": null,
  "statusUrl": "/api/provision/3f2a9c1e-5b7d-4e8a-9c0f-1a2b3c4d5e6f"
}

slug is made from the business name. If that slug is already taken, a number is added, such as example-plumbing-2. Keep siteId: you need it to check the build.

When builds are paused

Sometimes a valid request is not queued. You then get status 200 with "paused": true and a message. No site is queued and no credit is used. Try again later.

{
  "ok": true,
  "paused": true,
  "message": "Today's free builds are used up — try again tomorrow."
}

The message is either "Today's free builds are used up — try again tomorrow.", which applies to accounts that have only ever had signup credits, or "Free tests are paused right now — check back soon."

Check a build

GET /api/provision/{siteId}

Only the key that created the build can read it. Any other key gets the same 404 as an unknown ID.

curl "https://YOUR_DOMAIN/api/provision/3f2a9c1e-5b7d-4e8a-9c0f-1a2b3c4d5e6f" \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "status": "complete",
  "currentStep": "Site complete",
  "progressPct": 100,
  "previewUrl": "https://example-plumbing.example.com/",
  "adminUrl": "https://example-plumbing.example.com/wp-admin/",
  "warnings": [],
  "error": null,
  "liveAt": "2026-10-01T15:04:10.000Z",
  "enhancingStartedAt": "2026-10-01T15:04:11.000Z",
  "completedAt": "2026-10-01T15:06:30.000Z",
  "enhancementError": null,
  "creditRefunded": false
}

Response fields

There is no endpoint that lists your sites. Keep the siteId of each build you create.

Errors

Error responses have "ok": false and an error string. Validation errors also have a details list with one line per problem.

{
  "ok": false,
  "error": "Invalid provision request",
  "details": ["phone: required and must contain at least 10 digits"]
}