deploy.hosting.complete-bundle

Confirm a bundle upload: the deployment is served at its URLs

POST /deploy/api/apps/{id}/bundles/{deploymentId}/completeIAM deploy:DeployAppChanges stateDestructive

Fails while the upload is missing or its size differs from the one announced.

Request syntax

POST /deploy/api/apps/{id}/bundles/{deploymentId}/complete

Path parameters

  • idRequired

    string

    Constraints: uuid

  • deploymentIdRequired

    string

    Constraints: uuid

Response

200 with `data`: deploymentId, status, and `urls` — preview (the deployment’s own URL) and production (the app’s URL, or null for a preview).

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • deploymentIdAlways

    string

    The deployment
  • statusAlways

    one of queued, building, pushing, deploying, live, failed, superseded

    Its status now, live once served
  • urlsAlways

    object

    Where it is served
  • urls.​previewAlways

    string

    The deployment’s own URL
  • urls.​productionAlways

    string, may be null

    The app’s URL; null for a preview

Checked against the handlers: every route test validates their answers against this schema.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow deploy:DeployApp on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud deploy hosting complete-bundle id deploymentId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_deploy_hosting_complete-bundle.