Skip to main content
GET
/
v1
/
ai
/
workspace
/
blog
/
status
/
{record_id}
Check status of a blog-creation workflow
curl --request GET \
  --url https://api.lindo.ai/v1/ai/workspace/blog/status/{record_id} \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "done": true,
  "status": "complete",
  "record_id": "rec_abc123xyz789",
  "message": "Page published at /about",
  "poll_after_ms": 5000,
  "result": {
    "website_id": "website_def456",
    "blog_id": "blog_jkl012",
    "slug": "hello-world",
    "path": "/blog/hello-world"
  },
  "error": "Insufficient credits: daily limit reached"
}

Documentation Index

Fetch the complete documentation index at: https://lindo.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Enter your API key (starts with lindo_sk_)

Path Parameters

​
record_id
string
required

The workflow record_id returned by the create-blog endpoint

Example:

"rec_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"

​
record_id
string
required

The workflow record_id you polled

Example:

"rec_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 once the blog post has been published (status is complete).

​
error
string

When status is errored, a machine-readable error message

Example:

"Insufficient credits: daily limit reached"