Skip to main content
GET
cURL

Authorizations

Lovable-API-Key
string
header
required

Lovable API key. Send its value in the Lovable-API-Key header.

Headers

Lovable-Version
string

Stable API version to serve, as a YYYY-MM-DD date. Omit for the oldest supported stable version, currently 2026-09-11.

Lovable-Beta
string

Comma-separated beta revision strings to enable on top of the stable version.

Path Parameters

project_id
string
required

Project ID.

deployment_id
string
required

Deployment ID returned by POST /v1/projects/{project_id}/publish.

Response

OK

error_class
enum<string> | null
required

Where to address the failure; see the operation description for the action for each class. Null when no failure category is available. More values may be added; for unknown values, show error_message and contact support instead of automatically retrying.

Available options:
transient,
code,
configuration,
data,
integration,
policy,
internal,
null
error_message
string | null
required

Human-readable reason for a deployment failure; null unless the deployment failed.

id
string
required

Deployment ID.

status
enum<string>
required

Deployment progress. running means the deployment was accepted and has not reported completion. completed means the deployment succeeded and url is set. unknown means the deployment exists but its workflow state has no recognized public mapping; it confirms neither success nor failure. Poll again with backoff and a bounded timeout, then report an indeterminate result if it persists. Unknown or mismatched deployment IDs return HTTP 404. Clients must tolerate new values.

Available options:
running,
completed,
error,
unknown
url
string | null
required

URL produced by this successful deployment; null until this deployment succeeds, even when an older version is published.