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

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": "owner@example.com",
    "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": "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.

List templates

GET /api/templates

Returns the templates a new site can use, as a JSON list. No key is needed; a key that is sent must be valid. Send a template's templateId (and its themeId, when it has one) to POST /api/provision.

[
  { "id": "classic", "templateId": "template6", "themeId": "classic", "name": "Classic",
    "description": "Clean and modern, our standard look", "version": "2.0.0",
    "hasServices": true, "hasServiceAreas": true,
    "featureImage": "/img/look-picker/classic.jpg", "previewUrl": "/templates/ultimate?look=classic" }
]

Check a build from a workflow

POST /api/integrations/site-status

For workflow tools that can only send POST. Send {"siteId": "..."} with the same key. The answer is the same as GET /api/provision/{siteId}, plus ok, siteId and statusUrl. Same 401 and 404 rules.

White-label agency API

For agencies that take site requests from their own clients. Agency keys start with sf_agency_: on the API Keys page, pick Agency key before you click + Create New Key. Agency keys work only on the three routes below, and account keys do not work on them.

Templates

GET /api/agency/v1/templates

Returns templates (the same list as GET /api/templates) and themes (the themeId values you can send).

Create a site request

POST /api/agency/v1/site-requests

Takes every field of POST /api/provision, plus:

Check a site request

GET /api/agency/v1/site-requests/{requestId}

Any agency key on your account can read your requests. The answer has requestId, approvalStatus (pending, approved or rejected), status (the build status, or awaiting_approval / rejected before a build exists), siteId, siteUrl, previewUrl, adminUrl, progressPct, warnings and error.

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: must contain at least 10 digits"]
}