list_deployments

One call returns at most 10 publishes, and the response reports the total, in count over the HTTP API and in its first line over MCP, so page with offset 10, 20 and so on. Each row carries its _id, Status, Error, Build_Id, Deployment_Started_At, Deployment_Finished_At, Created_At and DeployHook.

A row whose Status is ready went live. failed and cancelled are the other endings, and any other status belongs to a publish still running or one that never finished.

A publish started through a deploy hook that still exists carries DeployHook with the name of that hook. DeployHook is null for every other publish, including one started by a hook that has since been deleted, so a null DeployHook does not prove a member started the publish.

Build logs and the file list are deliberately left out. Read the build output of a publish with get_publish_logs, and use get_publish_status for the publish happening now. See Publish history.

Inputs

Input	Type	Required	Description
projectId	string	Yes	The site id.
workspaceId	string	Yes	The workspace the site belongs to.
offset	integer	No	How many publishes to skip. Pages are 10 long, so use 0, then 10, then 20. Defaults to 0.