Theme upload
theme_uploadUpload a complete custom theme (Pro plan) as a new commit in its Git repo. Files are validated and compiled at once — a 422 lists every problem as path: message lines — then compiled in the background: poll theme_get until status is ready, then theme_publish. Without theme_id, role development reuses your one development theme and role unpublished creates a new theme; with theme_id it stores the next version of that theme. Updating the live theme needs allow_live: true.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"business_id": "<business_id>",
"files": "<files>"
},
"name": "theme_upload"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| role | No | development = your private work-in-progress theme (one per user, replaced on each upload); unpublished = a saved theme ready to publish | development |
| files | Yes | Theme files by path, e.g. {"sections/hero.liquid": "...", "config/settings_schema.json": "..."} | |
| message | No | Commit message | |
| theme_id | No | A theme id from theme_list (or the system theme id lokand-base) | |
| allow_live | No | With the live theme's id: update the live site in place | |
| business_id | Yes |