Skip to main content
GET
Check status of a website-creation workflow

Authorizations

Authorization
string
header
required

Enter your API key (starts with lindo_sk_)

Path Parameters

workflow_id
string
required

The workflow_id returned by the create-website endpoint

Example:

"wf_abc123xyz789"

Response

Status retrieved

success
enum<boolean>
required

The status poll succeeded. This is independent of whether the workflow itself succeeded; check status for that.

Available options:
true
Example:

true

done
boolean
required

True once the workflow has reached a terminal state (complete, partial, or errored). While false, clients should poll again after poll_after_ms.

Example:

true

status
enum<string>
required
  • scheduled: queued to run in the future
  • running: currently executing
  • complete: fully finished with no errors
  • partial: finished, but some sub-steps (e.g. individual pages of a website) failed
  • errored: the workflow itself failed
Available options:
scheduled,
running,
complete,
partial,
errored
Example:

"complete"

workflow_id
string
required

The workflow_id you polled

Example:

"wf_abc123xyz789"

message
string
required

Human-readable, safe-to-quote status message. Agents can surface this directly to end users.

Example:

"Page published at /about"

poll_after_ms
number

When done is false, suggested delay before the next status check, in milliseconds. Absent when done is true.

Example:

5000

result
object

Present as soon as the website record is created. While running, pages_summary and pages track per-page progress. When status is complete, every page succeeded; when partial, the website exists but one or more additional pages failed.

error
string

When status is errored, a machine-readable error message

Example:

"Insufficient credits: daily limit reached"