ReferenceProjects
Stamp content-as-code settings
Persist the repo's content_as_code flags as project-level state. Called by the CLI at upload time so the instance learns what the repo has opted into (Git-backed tracking and write-back).
POST/api/v1/projects/{projectUuid}/code/sync-settings
Authentication: personal access token. The spec defines an api_key security
scheme — send an Authorization: ApiKey <your-personal-access-token> header
(value format: ApiKey <your key>). A session_cookie scheme (connect.sid)
exists for browser sessions. Operations in this spec declare security: [], an
artifact of the upstream spec generator — authentication is still enforced by the
server.
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
projectUuid | string | Yes |
Request body
{
"path": "string",
"sync": true
}Responses
200 — Success
{
"results": "string",
"status": "ok"
}default — Error
{
"error": {
"data": "string",
"message": "string",
"name": "string",
"statusCode": 0
},
"status": "error"
}