A device posts its entries and the intervals they cover, idempotent on the entry id
Carries the device header (X-Six-Minute-Device); the body's device_id must be that device. Each entry is answered with one outcome: applied (written), unchanged (the row was already exactly this, so a replayed batch is not an error) or refused with a sentence saying what to fix. The cloud refuses an entry whose edited_at is set, because it is the person's from their first edit and the engine may not replace it (Row E); an accounting field moved on a released row; a row under another member's name; a matter that is not this firm's; and a hand-made entry (no as_judged) whose narrative is longer than the firm's length, narrative.max_chars or else 240, which an engine-written draft is not held to here (D-230). A body carrying a local-only field of an entry (summary, idle_ratio, observation_ids, assignment, assignment_ref, assigned_at, recording_id) is a 422 for the whole batch: those never leave the device (D-85). Each item carries the intervals its entry covers (D-215): each lies inside the entry's block, with every observation made during it, tagged by source and with no cap (a screen item is {source, t_start, t_end, app, bundle, title, host}, bundle being the application's identity, a Mac bundle id or a Windows app id or executable name, "" when unknown), and the text the judgment read, both sealed under the tenant key; the text is not stored under the confidential tier. The intervals are written with an applied item only: a refused or unchanged item writes none, and the replacement of an engine-owned draft replaces the intervals inside its block. An item whose intervals would overlap a stored interval of the author is refused. A new row's edges are checked on the grid at that point (D-219): a stored interval's edge, the item's own included, or a line of the day's unit (the firm's when the day opened, or now for a day not opened yet), never inside a stored interval; the stored intervals of the posting device and the earlier ids X-Six-Minute-Device-Known names, as the page snaps a hand-made entry (O12). An entry carries no billing field, no price and no durations: its hours are its block (D-218).
Request
- Base URLhttps://api.sixminute.ai (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
Request body
Response
One outcome per entry of the batch, in no promised order.
Changes
No recorded changes to this operation across all 2 revisions of this API.