From 4304c71bd8df5e2009bb682cd6ddb249e2db4ce3 Mon Sep 17 00:00:00 2001 From: Becky Conning Date: Sat, 29 Aug 2026 03:43:45 +0100 Subject: [PATCH] Match POST /pipelines' 201 body and the in-band state enum to the live API MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The live 201 from POST /pipelines is a bare JSON string (the id alone), not the {id} object this spec promised; and in-band dataset status reports scheming / initial-writing / initial-writing-completed, none of which the enum carried — initial-writing-completed being the terminal state of a finished in-band initial load. Both verified against staging 2026-08-29 while live-testing the files quickstart. Co-Authored-By: Claude Fable 5 --- reference/public-http-api.yaml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/reference/public-http-api.yaml b/reference/public-http-api.yaml index e2a125c..53c89fa 100644 --- a/reference/public-http-api.yaml +++ b/reference/public-http-api.yaml @@ -2415,12 +2415,11 @@ components: - sourceId id: title: '' - type: object - properties: - id: - type: string - required: - - id + description: >- + A bare JSON string holding the created resource's id. The live API + returns the id alone, not wrapped in an object (verified against + POST /pipelines on staging, 2026-08-29). + type: string pipeline-name: title: '' type: object @@ -2568,7 +2567,10 @@ components: enum: - discovered - staging + - scheming - writing + - initial-writing + - initial-writing-completed - waiting - written - failed