Endpoints — Records, POST
Every call in this family: what the card records, the edge cases that live on the call, and the verdict of every entry that measured it. Each of those lines names the door holding that entry's rules. The map is corpus/INDEX.md.
POST /entity/<type>
project is the requirement on every project-scoped type and the identity field is not, whatever the schema says. ?fields is ignored, and the 201 returns the whole record.
Omitting the identity field is not an error: the server writes
New Shot <id>and returns 201. Nothing is unique, so a re-run of an ingest doubles the rows rather than failing.?fields=codereturns 10 attribute keys, not one. Every write ignores it, so re-read the row when you need a dotted path or a narrowed set.An unknown field is a 400 here, unlike an unknown
fieldsname on a read, which is dropped at- Writes are loud about names; reads are silent.
created_atcomes back as2026-09-04 03:51:48 UTC, space separated, where a read returns2026-09-04T03:51:48Z. The same instant in two formats depending on the call.
Measured by
122_onset_entity_types(findings) — Slate, Camera, MocapTake, ShootDay and Scene create like Version:projectrequired,codegenerated. None hasattachments, and only Version.entity and Note.note_links reach them all.
rules:doors/findings-schema060_entity_dict_name(findings) — Thenamein an entity dict is the target'scached_display_name, filled on every type measured, single and multi alike. Read it, not the per-type identity field, and expect decoration.
rules:doors/findings-read150_group_resolution(findings) —task_assignees is <person>misses a Task assigned to their Group; filtertask_assignees.Group.users. Group assignment makes the members followers once, and an Artist reads Groups and members.
rules:doors/findings-filter011_create_project(findings) — A script user can create a Project with nothing but {"name": ...}, at 201, but the response echoes only 6 attributes, so read the project back if you need anything else.
rules:doors/findings-write012_create_version(findings) — The schema's mandatory flags are not the create contract: on every project-scoped type measured,projectis required and the identity field is optional, server-generated and not unique.
rules:doors/findings-write024_read_after_write(findings) — Every write ignores ?fields. A create returns what you sent plus the server defaults, an update returns the whole record, and neither resolves a dotted path, so re-read for those and after an upload.
rules:doors/findings-write058_local_storage_roots(findings) — One create fills everylocal_path_*the storage row defines, whichever platform's root the path was under. The server picks the deepest matching root, and no conditional-write header is honoured.
rules:doors/findings-write069_client_note(findings) —client_notecannot be set over REST:trueon create is 400 and anyPUTis 400editable on create only.sg_note_type: "Client"is the one marker a caller can write.
rules:doors/findings-write070_authored_timestamps(findings) — A create body sets created_at and updated_at and they read back exactly, on Note, Task and Version, though the schema flags both editable false; every PUT on either 400s.
rules:doors/findings-write078_page_setting_write(findings) — A script cannot create a Page (HumanUser expected), a person can. settings_json writes only as a JSON string, reads back identical. DELETE on a PageSetting is 400: every created row is permanent.
rules:doors/findings-write083_task_template_on_create(findings) — A create withtask_templatemakes the Tasks inside the same call, byPOSTand by_batch, copying every field set on the template tasks and their dependency types and offsets.
rules:doors/findings-write084_task_template_reapply(findings) — Changingtask_templateto T creates a Task per T task no Task links bytemplate_task, duplicating a same-name hand-made one, and re-syncs the linked Tasks' fields and edges (probe 102).
rules:doors/findings-write085_task_dependency_types(findings) — TaskDependency takes fourdependency_typevalues, defaultfinish-to-start-next-day;offset_dayscounts working days and snaps the dependent both ways.shift_ratiomoved nothing.
rules:doors/findings-write086_batch_tasks_with_dependencies(findings) — Tasks and their dependencies take two_batchcalls: create the Tasks, then create TaskDependency rows.upstream_taskson a create links without rescheduling.
rules:doors/findings-write087_dependency_cascade(findings) — An upstream date write reschedules every unpinned downstream Task, later and earlier alike; a null one moves none (097). A pinned Task stays put and flagsdependency_violationwhile broken.
rules:doors/findings-write092_dependency_edge_reschedule(findings) — A new edge reschedules an unpinned downstream Task at once, whether POSTed or copied by a template apply on claim. A pinned one keeps its dates and flagsdependency_violation.
rules:doors/findings-write093_clear_dates_pin(findings) — On a dependent Task a start_date write pins it, null or real; a due_date write never does, null or real. A pinned null Task holds; PUT pinned:false refills both dates.
rules:doors/findings-write094_permission_preflight(findings) — Ask with a write that cannot land: a no-op PUT per field (update), a POST with a bad status (create), a _batch of [delete, 404 sentinel] (delete). Permission is checked first, and nothing is written.
rules:doors/findings-write095_dependency_remove_undo(findings) — Remove an edge withDELETEon its TaskDependency row: revive restores its type and offset. Aremoveonupstream_tasksordownstream_taskserases the row for good.
rules:doors/findings-write097_null_dates_unpin(findings) — A Task with no upstream never pins, on a null or a real date write; nulling its dates leaves its downstream unmoved, and pinned:false refills nothing.
rules:doors/findings-write098_template_merge_in_one_batch(findings) — Recipe 015's merge fits one_batch: requests run in order, so atask_templatewrite sees claims made earlier in the batch, andnullthenTon the same Shot re-runs the apply.
rules:doors/findings-write099_template_apply_edge_copy_kept(findings) — A template apply copies a missing edge between two Tasks whosetemplate_taskalready match it, whether either was claimed, kept, or created by that same call.
rules:doors/findings-write100_duration_write_pin(findings) — Writing duration on a dependent Task does not pin it; a start_date write in the same run does. It keeps following the upstream, and a duration write upstream moves it.
rules:doors/findings-write101_template_edge_conflict(findings) — On a claimed pair, a template apply replaces an existing edge of another type, or the reverse edge, with the template's edge: the old row is erased, not retired, and the PUT is a plain 200.
rules:doors/findings-write102_task_template_resync(findings) — Writing task_template T re-syncs every Task linked to T: T's non-empty values overwrite, status kept, dates and assignees kept or filled if empty; edges between linked Tasks reset to T's.
rules:doors/findings-write105_offset_days_null_vs_zero(findings) — TaskDependencyoffset_daysnull and 0 are stored and compared as different: a template apply deletes an entity edge with null against a template 0 (or the reverse) and re-creates it with a new id.
rules:doors/findings-write106_template_task_linked_twice(findings) — With two Tasks linked to one template task, an apply re-syncs and wires only one of them, picked unpredictably (not by id, age or edges); the other is left as is. No error, nothing duplicated.
rules:doors/findings-write107_dependency_three_task_loop(findings) — A three-Task loop is a 400 on a direct create and inside_batch, which rolls back whole. A template apply deletes a claimed Task's upstream edge from a Task outside the template, loop or not.
rules:doors/findings-write108_task_template_resync_empties(findings) — Re-sync to T: a numeric 0 on T's task overwrites (est, duration); milestone false and "" (stored null) keep the Task's value; a Task with only start or only due keeps its null duration.
rules:doors/findings-write109_template_apply_outside_edge(findings) — A template apply erases an edge where a linked Task depends on a Task not linked to the template (root or not, other template, other Shot); it kept the edge with the outside Task downstream.
rules:doors/findings-write111_template_undo_outside_edge(findings) — An undo's write back to template A erases every edge whose downstream Task is A-linked and that A lacks, pre-merge edges included; recipe 022 DELETEs one such edge, 404s and rolls back.
rules:doors/findings-write112_template_unmerge_linked_twice(findings) — Undo relinking two Tasks to one template task: A wires either one (11 of 14 picked the loser), nothing is made. Relink the loser after the task_template write: then it matches the one-link undo.
rules:doors/findings-write113_batch_atomic_after_template_write(findings) — A_batchholding atask_templateapply is atomic: a later or earlier failing request left no Task, no claim, no field write, no edge and no EventLogEntry row.
rules:doors/findings-write127_retry_and_client_uuid(findings) — A text field created withunique: truerefuses a second create with the same value, case and outer spaces ignored, in a batch too. It is the only idempotency key: the API has no header for it.
rules:doors/findings-write136_unique_scope_retired(findings) — A deleted row frees itsuniquevalue: a new row may take it. Reviving the old row while another holds the value is a 400 code 104 PG transaction error, and the row stays retired.
rules:doors/findings-write137_batch_create_coercion(findings) — A_batchcreate on a custom entity takes a numeric string in a float and honourscreated_at, as a single POST does. It also takes an Integer and"1e3", which a single POST refuses.
rules:doors/findings-write143_nonadmin_rows(findings) — On the probed site an Artist may not create, edit or delete custom-entity rows (status only) and may create but not delete an Attachment, its own included. The group rights call predicts each answer.
rules:doors/findings-write145_time_fields(findings) — date_time rounds to the second on POST and PUT (.999 goes up, .5 stays) but truncates in a _batch create. A new timecode field has no rate property; it is integer ms rendered at the site's fixed rate.
rules:doors/findings-write146_note_unique_key(findings) — Aunique: truetext field works on Note as on Version (probe 127), and refuses a duplicate on PUT and under sudo too. ANote.metakey is found bycontains, case-sensitive, and enforces nothing.
rules:doors/findings-write148_note_author_fields(findings) —userandcreated_byare both honoured on a Note or Version create, though the schema flagscreated_byread only; a PUT to it is 400. Under sudo_as_login all three author fields are the person.
rules:doors/findings-write156_action_menu_item(findings) — An ActionMenuItem creates from{}at 201 andurlis not checked; an Artist is refused. Run from the web interface, an httpurlgot a form POST in a new tab,jsonor not, with no token.
rules:doors/findings-write161_link_to_deleted_row(findings) — A link to a deleted row is hidden, not removed: it reads null or drops out, and returns on revive, even after a replace. A write naming a deleted row is 400 code 104Value is not legal.
rules:doors/findings-write164_vendor_writes(findings) — On the probed site a Vendor creates no Bid or Bid Line, by POST or_batch, and updates onlysg_status_list, each refusal 400 code 104. Both preflight reads predicted every answer.
rules:doors/findings-write168_group_create_rights(findings) — On the probed site a Manager or Admin person creates, renames, re-members and retires any Group; Artist and Vendor get 400 code 104. The person's own group rights on Group predict each answer.
rules:doors/findings-write151_video_on_take(findings) — Onsg_uploaded_movieanHEVC.mov becomes an H.264 mp4 with a thumbnail and a filmstrip, ready in under a minute. As a plain Attachment, video gets a 480 px thumbnail and nothing else.
rules:doors/findings-upload152_audio_on_take(findings) — Audio onsg_uploaded_movietranscodes to an audio-only mp4 (aac), status 1, no thumbnail. The storedcontent_typeis not the PUT's: an Opus.webmsent asaudio/webmreadsvideo/webm.
rules:doors/findings-upload025_event_log(findings) — meta.old_value and meta.new_value answer "what was this before", but meta is unfilterable and unsortable: narrow on entity, event_type and attribute_name, sort -id, read meta yourself.
rules:doors/findings-observe049_script_events(findings) — A script's writes reach the event log only while its ApiUser has generate_event_log_entries True. The default is False and nothing errors when off. One create logs one row per field plus one _New.
rules:doors/findings-observe067_notes_in_the_stream(findings) — A Reply reaches every linked stream in 33 s ascreate_reply, creates too; a script's Note create and status changes were absent after 430 s. Write as a person.
rules:doors/findings-observe090_template_task_events(findings) — A template-generated Task logs like a hand-made one plus atemplate_taskchange row,in_createtrue, credited to the caller. Filterattribute_nametemplate_taskto find them.
rules:doors/findings-observe124_updated_at_bumps(findings) —updated_atmoves on a write, a finished upload and its transcode, and on a link set from either end, but not on a no-op PUT and not when a Note names the row innote_links.
rules:doors/findings-observe147_note_addressing(findings) — A Note's To and cc people, and every member of an addressed Group, become its followers at create, with the author. Find a person's Notes withaddressings_to.Group.usersas well asaddressings_to.
rules:doors/findings-observe149_note_update_activity(findings) — A person's Note create streams at once; a PUT tocontentoraddressings_towrites no stream row in 150 s but turns the addressee back to unread. An addressee added later follows at once.
rules:doors/findings-observe001_publish_version_with_media(recipes) — Publish a generated image to Flow PT as a Version, with provenance and the workflow attached
rules:doors/recipes004_register_published_file(recipes) — Register the next PublishedFile without overwriting the last one, and write a path the server resolves for every platform
rules:doors/recipes007_build_and_reconcile_a_cut(recipes) — Write a Cut and its CutItems from an edit, read the timeline back, and reconcile a second edit against the Cut already there
rules:doors/recipes008_delivery_progress(recipes) — Keep a Delivery honest about what a long transfer is doing, including when it is cancelled and when it crashes
rules:doors/recipes013_publish_file_bytes(recipes) — Publish a file's bytes onto a PublishedFile when the caller has no LocalStorage root to write under
rules:doors/recipes017_check_permission_before_writing(recipes) — Learn whether the signed-in person may update, create or delete a type before writing, with calls that change nothing
rules:doors/recipes025_retry_safe_create(recipes) — Create rows from a client that retries after timeouts, without duplicating any row
rules:doors/recipes026_note_per_shot(recipes) — Keep one Note per Shot, addressed to the people on the Shot's Tasks, found again by a client key and updated in place
rules:doors/recipes027_media_on_a_take(recipes) — Put a video or audio clip on a custom entity row so a browser can play it, and know when it is ready
rules:doors/recipes030_create_a_group_as_a_person(recipes) — Create a Group as the signed-in person, once their permission group allows it, without a second Group of the same name
rules:doors/recipes
Silent on this call
post_entity_type—projectis the requirement on every project-scoped type and the identity field is not, whatever the schema says.?fieldsis ignored, and the 201 returns the whole record.024_read_after_write— Every write ignores ?fields. A create returns what you sent plus the server defaults, an update returns the whole record, and neither resolves a dotted path, so re-read for those and after an upload.058_local_storage_roots— One create fills everylocal_path_*the storage row defines, whichever platform's root the path was under. The server picks the deepest matching root, and no conditional-write header is honoured.086_batch_tasks_with_dependencies— Tasks and their dependencies take two_batchcalls: create the Tasks, then create TaskDependency rows.upstream_taskson a create links without rescheduling.025_event_log— meta.old_value and meta.new_value answer "what was this before", but meta is unfilterable and unsortable: narrow on entity, event_type and attribute_name, sort -id, read meta yourself.049_script_events— A script's writes reach the event log only while its ApiUser has generate_event_log_entries True. The default is False and nothing errors when off. One create logs one row per field plus one _New.067_notes_in_the_stream— A Reply reaches every linked stream in 33 s ascreate_reply, creates too; a script's Note create and status changes were absent after 430 s. Write as a person.
corpus/endpoints/post_entity_type.md
POST /entity/<type>/<id>
Revives a retired row. ?revive=1 is required and any JSON body is discarded, so this is not an update via POST.
| you send | result |
|---|---|
?revive=1, ?revive=true, ?revive=yes |
revived |
?revive=0, ?revive=false |
400 revive must be true |
no revive parameter |
400 revive is missing |
| a body of field values | 200, the fields are not applied |
?fields=code |
200, no attributes returned either way |
The response has no
attributeskey at all, which is thinner than any other write returns. Re-read the id to see the record.Field values survive the retire and come back with the revive. Nothing is reset.
did_revive: falseat 200 is the only signal that the row was already live. Readmeta, not the status code.
Measured by
048_one_record_beyond_crud(findings) — POST on one record is revive, not update:?revive=1is required and the body is ignored./<field>reads image and attachment fields only, andrelationships/<field>is the same data, unpaged.
rules:doors/findings-read089_task_delete_side_effects(findings) — Deleting a Task retires its TaskDependency rows, unlinks both neighbours without bridging them, and nullsVersion.sg_taskandPublishedFile.task. Revive restores all of it.
rules:doors/findings-write095_dependency_remove_undo(findings) — Remove an edge withDELETEon its TaskDependency row: revive restores its type and offset. Aremoveonupstream_tasksordownstream_taskserases the row for good.
rules:doors/findings-write103_batch_delete_revive(findings) — Adeleteinside_batchretires a Task or TaskDependency exactly asDELETEdoes: same retired read-back, and revive returns the same id, fields, edges andVersion.sg_task.
rules:doors/findings-write110_template_task_after_revive(findings) — Revive restorestemplate_task. A task_template write while the Task is retired re-creates it, so a later revive leaves two Tasks on one template task. Revive first, then write.
rules:doors/findings-write136_unique_scope_retired(findings) — A deleted row frees itsuniquevalue: a new row may take it. Reviving the old row while another holds the value is a 400 code 104 PG transaction error, and the row stays retired.
rules:doors/findings-write161_link_to_deleted_row(findings) — A link to a deleted row is hidden, not removed: it reads null or drops out, and returns on revive, even after a replace. A write naming a deleted row is 400 code 104Value is not legal.
rules:doors/findings-write018_remove_and_restore_a_dependency(recipes) — Remove one dependency between two Tasks and put it back on undo, with its type and offset
rules:doors/recipes021_undo_a_batch_delete(recipes) — Delete Tasks or dependencies in one batch and undo it by reviving the same rows
rules:doors/recipes
Silent on this call
048_one_record_beyond_crud— POST on one record is revive, not update:?revive=1is required and the body is ignored./<field>reads image and attachment fields only, andrelationships/<field>is the same data, unpaged.
corpus/endpoints/post_entity_type_id.md
POST /entity/_batch
The key is requests, not data, and sending data is 400 requests is missing. It answers 200 rather than 201, and one bad request rolls the whole batch back.
It is atomic. The Shot the first request would have created does not exist after the 404.
The response nesting is the trap that outlives a run. Reading
row["id"]instead ofrow["data"]["id"]yieldsNone, so cleanup silently skips the rows and they stay on the site.A returned id does not by itself prove the row exists. Read back after a batch that matters.
The request key and the response key differ by name.
requestsin,dataout.
Measured by
028_loud_and_silent(findings) — A 400 is trustworthy and usually names the legal set, but a 200 proves nothing: an unknown field, sort key or query param is a no-op, and a batch can return an id for a row it never made.
rules:doors/findings-protocol024_read_after_write(findings) — Every write ignores ?fields. A create returns what you sent plus the server defaults, an update returns the whole record, and neither resolves a dotted path, so re-read for those and after an upload.
rules:doors/findings-write083_task_template_on_create(findings) — A create withtask_templatemakes the Tasks inside the same call, byPOSTand by_batch, copying every field set on the template tasks and their dependency types and offsets.
rules:doors/findings-write084_task_template_reapply(findings) — Changingtask_templateto T creates a Task per T task no Task links bytemplate_task, duplicating a same-name hand-made one, and re-syncs the linked Tasks' fields and edges (probe 102).
rules:doors/findings-write086_batch_tasks_with_dependencies(findings) — Tasks and their dependencies take two_batchcalls: create the Tasks, then create TaskDependency rows.upstream_taskson a create links without rescheduling.
rules:doors/findings-write092_dependency_edge_reschedule(findings) — A new edge reschedules an unpinned downstream Task at once, whether POSTed or copied by a template apply on claim. A pinned one keeps its dates and flagsdependency_violation.
rules:doors/findings-write094_permission_preflight(findings) — Ask with a write that cannot land: a no-op PUT per field (update), a POST with a bad status (create), a _batch of [delete, 404 sentinel] (delete). Permission is checked first, and nothing is written.
rules:doors/findings-write098_template_merge_in_one_batch(findings) — Recipe 015's merge fits one_batch: requests run in order, so atask_templatewrite sees claims made earlier in the batch, andnullthenTon the same Shot re-runs the apply.
rules:doors/findings-write099_template_apply_edge_copy_kept(findings) — A template apply copies a missing edge between two Tasks whosetemplate_taskalready match it, whether either was claimed, kept, or created by that same call.
rules:doors/findings-write101_template_edge_conflict(findings) — On a claimed pair, a template apply replaces an existing edge of another type, or the reverse edge, with the template's edge: the old row is erased, not retired, and the PUT is a plain 200.
rules:doors/findings-write103_batch_delete_revive(findings) — Adeleteinside_batchretires a Task or TaskDependency exactly asDELETEdoes: same retired read-back, and revive returns the same id, fields, edges andVersion.sg_task.
rules:doors/findings-write104_template_unmerge_in_one_batch(findings) — Recipe 019's undo fits one_batchwith the same end state, if the batch skips edges its own task_template write removes: deleting one 404s and rolls back all. Undo to null deletes them.
rules:doors/findings-write107_dependency_three_task_loop(findings) — A three-Task loop is a 400 on a direct create and inside_batch, which rolls back whole. A template apply deletes a claimed Task's upstream edge from a Task outside the template, loop or not.
rules:doors/findings-write109_template_apply_outside_edge(findings) — A template apply erases an edge where a linked Task depends on a Task not linked to the template (root or not, other template, other Shot); it kept the edge with the outside Task downstream.
rules:doors/findings-write110_template_task_after_revive(findings) — Revive restorestemplate_task. A task_template write while the Task is retired re-creates it, so a later revive leaves two Tasks on one template task. Revive first, then write.
rules:doors/findings-write111_template_undo_outside_edge(findings) — An undo's write back to template A erases every edge whose downstream Task is A-linked and that A lacks, pre-merge edges included; recipe 022 DELETEs one such edge, 404s and rolls back.
rules:doors/findings-write112_template_unmerge_linked_twice(findings) — Undo relinking two Tasks to one template task: A wires either one (11 of 14 picked the loser), nothing is made. Relink the loser after the task_template write: then it matches the one-link undo.
rules:doors/findings-write113_batch_atomic_after_template_write(findings) — A_batchholding atask_templateapply is atomic: a later or earlier failing request left no Task, no claim, no field write, no edge and no EventLogEntry row.
rules:doors/findings-write127_retry_and_client_uuid(findings) — A text field created withunique: truerefuses a second create with the same value, case and outer spaces ignored, in a batch too. It is the only idempotency key: the API has no header for it.
rules:doors/findings-write137_batch_create_coercion(findings) — A_batchcreate on a custom entity takes a numeric string in a float and honourscreated_at, as a single POST does. It also takes an Integer and"1e3", which a single POST refuses.
rules:doors/findings-write145_time_fields(findings) — date_time rounds to the second on POST and PUT (.999 goes up, .5 stays) but truncates in a _batch create. A new timecode field has no rate property; it is integer ms rendered at the site's fixed rate.
rules:doors/findings-write154_batch_multi_entity_mode(findings) —multi_entity_update_modein a_batchupdate'sdataadds, removes and sets as on a PUT, and several updates of one record in one batch apply in request order, each row echoing the state after it.
rules:doors/findings-write161_link_to_deleted_row(findings) — A link to a deleted row is hidden, not removed: it reads null or drops out, and returns on revive, even after a replace. A write naming a deleted row is 400 code 104Value is not legal.
rules:doors/findings-write164_vendor_writes(findings) — On the probed site a Vendor creates no Bid or Bid Line, by POST or_batch, and updates onlysg_status_list, each refusal 400 code 104. Both preflight reads predicted every answer.
rules:doors/findings-write002_batch(recipes) — Apply many creates, updates and deletes in one atomic call, and match the results back to the requests
rules:doors/recipes005_propagate_status(recipes) — Roll a status up from a parent's Tasks and Versions onto the parent, without racing a concurrent write
rules:doors/recipes007_build_and_reconcile_a_cut(recipes) — Write a Cut and its CutItems from an edit, read the timeline back, and reconcile a second edit against the Cut already there
rules:doors/recipes009_multi_entity_safely(recipes) — Add to and remove from a multi_entity field without destroying the links you did not mean to touch
rules:doors/recipes015_apply_task_template_without_duplicates(recipes) — Apply a task template to an entity that already has Tasks, without duplicating the ones it already holds
rules:doors/recipes016_create_tasks_with_dependencies(recipes) — Create a set of Tasks and the dependencies between them, with types and offsets, in two calls
rules:doors/recipes017_check_permission_before_writing(recipes) — Learn whether the signed-in person may update, create or delete a type before writing, with calls that change nothing
rules:doors/recipes020_apply_task_template_in_one_batch(recipes) — Apply a task template to an entity that already has Tasks, without duplicates, in one atomic call
rules:doors/recipes021_undo_a_batch_delete(recipes) — Delete Tasks or dependencies in one batch and undo it by reviving the same rows
rules:doors/recipes022_undo_task_template_merge_in_one_batch(recipes) — Undo a task template merge in one atomic call, returning Tasks, fields and dependencies to their state before it
rules:doors/recipes023_undo_task_template_merge_with_a_task_linked_twice(recipes) — Undo a task template merge when two Tasks pointed at the same old template task, without the server picking which one gets the edges
rules:doors/recipes025_retry_safe_create(recipes) — Create rows from a client that retries after timeouts, without duplicating any row
rules:doors/recipes001_batch_create_skips_validation(reports) — A create inside POST /entity/_batch skips the required-attribute validation the single-create path applies, and answers 200 with the id of a row no read can reach.
rules:doors/reports
Silent on this call
post_entity_batch— The key isrequests, notdata, and sendingdatais 400requests is missing. It answers 200 rather than 201, and one bad request rolls the whole batch back.028_loud_and_silent— A 400 is trustworthy and usually names the legal set, but a 200 proves nothing: an unknown field, sort key or query param is a no-op, and a batch can return an id for a row it never made.024_read_after_write— Every write ignores ?fields. A create returns what you sent plus the server defaults, an update returns the whole record, and neither resolves a dotted path, so re-read for those and after an upload.086_batch_tasks_with_dependencies— Tasks and their dependencies take two_batchcalls: create the Tasks, then create TaskDependency rows.upstream_taskson a create links without rescheduling.002_batch— Apply many creates, updates and deletes in one atomic call, and match the results back to the requests005_propagate_status— Roll a status up from a parent's Tasks and Versions onto the parent, without racing a concurrent write009_multi_entity_safely— Add to and remove from a multi_entity field without destroying the links you did not mean to touch
corpus/endpoints/post_entity_batch.md