Edit is not available via the API
Editing a diary entry stays in the app (spec: manual edits happen on the entry's detail page, where the role × field matrix and the entry's History live). This verb is answered with a `405` pointing there.
Editing a diary entry stays in the app (spec: manual edits happen on the
entry's detail page, where the role × field matrix and the entry's History
live). This verb is answered with a 405 pointing there.
The per-tenant API key, copied from Settings → API & integrations.
Sent as the x-api-key request header. The key is tenant-scoped and acts
with Admin-equivalent, tenant-wide access.
In: header
Response Body
application/json
curl -X PATCH "https://example.com/diary-entries"{ "error": { "code": "method_not_allowed", "message": "This resource is read-only via the API. Edit it in the FOREMAN app." }}Request a presigned diary-photo upload URL POST
**Step 1 of the presigned diary-photo upload** — the image-only sibling of the document upload. Validates the declared image (JPG/PNG only — no PDF) and returns a short-lived, single-use **signed PUT URL** (`uploadUrl`) plus the computed `storagePath`. **The image bytes never travel through this API call.** After this returns, the caller PUTs the raw image bytes directly to `uploadUrl` (a plain HTTP `PUT` with the file as the request body and the matching `Content-Type`) — out of band — then passes the returned `storagePath` in the `photoPaths` array of `POST /diary-entries`. **There is no register step**: creating the diary entry writes the `diary_photo` row(s) (ADR 0001 §5). Any crew member assigned to the project may log diary photos (not manager-only); an Admin/API key is implicitly on every project. Blocked on read-only/archived projects. **Photos must be 2 MB or smaller.** The limit is enforced by Storage on the PUT itself, so an oversized upload fails at that step rather than here — this call only sees the *declared* file. Resize before uploading: 1600px on the long edge is plenty, and is what the FOREMAN app sends.
Create a document folder POST
Creates a folder in one of a project's document libraries. Names are unique per project and library, **case-insensitively** — "Drawings" and "drawings" are the same folder, and a collision returns `409`. Admin or the project's Site Manager; blocked on read-only tenants and archived projects, like every other write on these libraries.