Update a project
Every field is optional, and a field sent replaces the stored one: to change one output, send the whole config. Changing config or buildVersion of a running project restarts its processing service with the new instructions; files already done are not processed again. If the running service cannot be stopped, the answer is 502 and nothing is stored. If the restarted service does not start, the change is stored and the answer is 422 service_start_failed: the project reads error until POST …/start succeeds.
Guide: Projects
Authorizations
A token from POST /token/create, made with your API key pair.
Path Parameters
The project id, a lowercase ULID.
^[0-9a-z]{26}$Body
2552000The processing instructions, validated against the schema of the project’s build. Shown here: build 0.9.0-alpha1-2026-10-20T14-10Z-3f05aa; GET /schema has any build’s.
Whether a new file starts a stopped project; see startOnNewFiles on create.
Where the project keeps its input and output folders: one of your storage connections — your own bucket — with a folder for each, or connectionId: null for SyncWords’ storage. Left out on create, your account’s default decides; left out on a change, nothing moves. A project on your own bucket reads its input folder and writes its output folder: no feed source, no feed outputs.
Response
OK