Aller au contenu principal

Create a Design from a portable archive

POST 

/artifacts/archives

Creates a Design from a v1 or v2 portable zip that GET /artifacts/{artifactId}/versions/{versionId}/archive (or the app's source download) produced. Send it as multipart/form-data with the zip in the field file (up to 264 MiB for v2, 26 MiB for v1) and a JSON field metadata with the idempotencyKey. The zip's files and assets are validated and the assets get fresh IDs. The Design is stored as written by the tool in metadata.tool (default other), its build is queued, and source-quality findings come back as warnings. A zip with credential-shaped text, files named like AI tool or editor settings, unsupported or unsafe entries (path tricks, links, encrypted entries) or contents that do not match the archive's own inventory is refused with 400, as is a title or description with credential-shaped text. Refused source paths report agent_config_name, invalid_path or reserved_build_file. The whole body must arrive within 120 seconds (later: 408, reason upload_timeout, and the connection is closed). A person has one archive upload at a time and the server a few: another answers 503, reason upload_busy, with Retry-After. A move from an archive queues a build, so it spends a unit of the budget of Design pushes and checks per token and per workspace: when it is used up the answer is 429 with Retry-After, reason push_budget, before the body is read; when the budget cannot be read, 503 with reason budget_unavailable. Needs a token with the Designs permission.

Request​

Responses​

Default Response