Get publish status

1. 1

   Save the deployment ID returned from your initial publish request.

   You need this unique identifier to track the progress of that specific build.

2. 2

   Send a GET request to /v1/projects/{project_id}/publish/{deployment_id} with your API key.

   This queries Lovable for the current status of your background publish task.

3. 3

   Repeat the request every 2 to 10 seconds until the status is completed or returns an error.

   Deployments take time to process in the background, but checking faster than every 2 seconds will trigger rate limits.

4. 4

   Inspect the error_class value if deployment fails to see whether to fix code, update settings, or contact support.

   Certain errors require fixing app code or permissions, while transient errors can be safely retried.

Create a TypeScript function to check the status of a Lovable deployment by calling GET https://api.lovable.dev/v1/projects/{project_id}/publish/{deployment_id}. The function should poll every 2 to 10 seconds, respect Retry-After headers on HTTP 429 rate limits, and resolve with the live URL when completed or reject with the error class and error message if publishing fails.

Polling

Repeatedly asking the server for updates on a timer until a background task finishes.

Async publish

A publishing job that runs in the background so you do not have to keep a single connection open while waiting.

• Do not request the status more than once every 2 seconds, or you will trigger rate limits.
• Always respect the Retry-After header if you receive an HTTP 429 rate limit response.
• Do not automatically retry publishing if the error class is code, configuration, or data; fix the underlying issue first.