Skip to content
Eternify Labs

What changed, and when.

Each release lists what it added, changed and retired. A stable operation is retired with 365 days’ notice and a beta one with 30, and a retired operation names its replacement.

Release 0004

2026-11-14

This release carries 2 accepted breaking changes to answers of the contract, made in place, once, before any outside client existed (ADR 0166 amendment (docs/specs/jobs-all-or-nothing-2026-11-11.md, section 8)). Each is listed below with its reason and named in releases/accepted-breaks.json. From the next release a break is a new operation plus a deprecation.

  • removed the schema `ProposePromotionResponse`

  • added the required property `data/items/jobId` to the response with the `200` status

    GET /v1/promotions

  • added the required property `jobId` to the response with the `202` status

    POST /v1/promotions

  • added the required property `jobId` to the response with the `200` status

    GET /v1/promotions/{promotionId}

  • added the success response with the status `202`

    POST /v1/promotions/{promotionId}/apply

  • Breaking, accepted: applyPromotion answers 202 job_started instead of 200: the apply of an approved promotion is a PROMOTION_APPLY job, because up to PROMOTION_MAX_CHANGES (200) customisation changes ran inside the approval's own request transaction under a 60 second bound, longer than the ledger's 30 second request timeout. It is replay only, reached through approveOperationProposal, so no outside client calls it directly. (ADR 0166 amendment (docs/specs/jobs-all-or-nothing-2026-11-11.md, section 8), 2026-11-14; 1 findings over 1 operations)

  • Breaking, accepted: A promotion reads APPLYING while its PROMOTION_APPLY job is open (PROPOSED with an open job; never stored), so the person sees the apply is under way instead of a promotion that looks undecided. It is the derived state the job conversion owes the readers of a promotion (docs/specs/jobs-all-or-nothing-2026-11-11.md, section 5), carried in place with the 202 move of applyPromotion, before any outside client: the company has no customer and no customer holds an API key. (ADR 0166 amendment (docs/specs/jobs-all-or-nothing-2026-11-11.md, section 8), 2026-11-14; 3 findings over 3 operations)

Release 0003

2026-11-13

  • added the optional property `data/items/indexJobId` to the response with the `200` status

    GET /v1/custom-fields

  • added the optional property `indexJobId` to the response with the `201` status

    POST /v1/custom-fields

  • added the optional property `indexJobId` to the response with the `200` status

    PATCH /v1/custom-fields/{definitionId}

  • added the success response with the status `202`

    PATCH /v1/custom-fields/{definitionId}

  • added the optional property `indexJobId` to the response with the `200` status

    POST /v1/custom-fields/{definitionId}/archive

  • added the optional property `indexJobId` to the response with the `200` status

    POST /v1/custom-fields/{definitionId}/restore

  • added the success response with the status `202`

    POST /v1/customers

Release 0002

2026-11-11

This release carries 5 accepted breaking changes to answers of the contract, made in place, once, before any outside client existed (ADR 0173). Each is listed below with its reason and named in releases/accepted-breaks.json. From the next release a break is a new operation plus a deprecation. The error `code` of a problem and of a failed job, and the job `kind`, are published in this release as strings whose known values are listed in `x-extensible-enum`, and a job result is an object with a `kind` and the shapes known today in `x-known-variants`. A new code, kind or result shape is no longer a change to the contract. oasdiff does not judge this a break, but a client that switched on the closed lists must now handle a value it does not know.

  • removed the schema `AutoCompleted`

  • removed the schema `Kind`

  • removed the schema `ListCustomFieldDefinitionsResponseItem`

  • removed the schema `ListCustomersResponseItem`

  • removed the schema `TieOut`

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/capital-purchases/look-back

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/capital-purchases/look-back

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/capital-purchases/look-back

  • added the optional property `data/items/indexState` to the response with the `200` status

    GET /v1/custom-fields

  • added the optional property `indexState` to the response with the `201` status

    POST /v1/custom-fields

  • added the optional property `indexState` to the response with the `200` status

    PATCH /v1/custom-fields/{definitionId}

  • added the optional property `indexState` to the response with the `200` status

    POST /v1/custom-fields/{definitionId}/archive

  • added the optional property `indexState` to the response with the `200` status

    POST /v1/custom-fields/{definitionId}/restore

  • removed `#/components/schemas/ListCustomersResponseItem` from the response body `anyOf` list for the response status `201`

    POST /v1/customers

  • added the success response with the status `202`

    POST /v1/events/projections/{projection}/replay

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `data/items/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    GET /v1/export/requests

  • the `data/items/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    GET /v1/export/requests

  • added the required property `data/items/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `200` status

    GET /v1/export/requests

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `201`

    POST /v1/export/requests

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `201`

    POST /v1/export/requests

  • the `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `201`

    POST /v1/export/requests

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `201`

    POST /v1/export/requests

  • added the required property `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `201` status

    POST /v1/export/requests

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `201` status

    POST /v1/export/requests

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/export/requests/{requestId}/approve

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/export/requests/{requestId}/approve

  • the `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/export/requests/{requestId}/approve

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/export/requests/{requestId}/approve

  • added the required property `anyOf[#/components/schemas/RequestFullExportResponseOption1]/job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/export/requests/{requestId}/approve

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/export/requests/{requestId}/approve

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/export/requests/{requestId}/decline

  • the `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/export/requests/{requestId}/decline

  • added the required property `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/export/requests/{requestId}/decline

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/export/requests/{requestId}/withdraw

  • the `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/export/requests/{requestId}/withdraw

  • added the required property `job/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/export/requests/{requestId}/withdraw

  • added the new enum value `CHART_IMPORT_APPLY` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `CSV_IMPORT` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `CUSTOM_FIELD_INDEX` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `PERIOD_CLOSE` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `PROJECTION_REPLAY` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `PROMOTION_APPLY` to the `query` request parameter `kind`

    GET /v1/jobs

  • added the new enum value `WORKSPACE_IMPORT_APPLY` to the `query` request parameter `kind`

    GET /v1/jobs

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `data/items/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    GET /v1/jobs

  • the `data/items/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    GET /v1/jobs

  • added the required property `data/items/result/anyOf[subschema #1]/kind` to the response with the `200` status

    GET /v1/jobs

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/jobs/bulk-operations

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/jobs/bulk-operations

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/jobs/bulk-operations

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    GET /v1/jobs/{jobId}

  • the `result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    GET /v1/jobs/{jobId}

  • added the required property `result/anyOf[subschema #1]/kind` to the response with the `200` status

    GET /v1/jobs/{jobId}

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/jobs/{jobId}/cancel

  • the `result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/jobs/{jobId}/cancel

  • added the required property `result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/jobs/{jobId}/cancel

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/jobs/{jobId}/pause

  • the `result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/jobs/{jobId}/pause

  • added the required property `result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/jobs/{jobId}/pause

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/jobs/{jobId}/reinstate

  • the `result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/jobs/{jobId}/reinstate

  • added the required property `result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/jobs/{jobId}/reinstate

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    POST /v1/jobs/{jobId}/resume

  • the `result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    POST /v1/jobs/{jobId}/resume

  • added the required property `result/anyOf[subschema #1]/kind` to the response with the `200` status

    POST /v1/jobs/{jobId}/resume

  • endpoint added

    GET /v1/openapi.json

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/purchases-exports

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/purchases-exports

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/purchases-exports

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/purchases-settings/paper-requirements/apply

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/purchases-settings/paper-requirements/apply

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/purchases-settings/paper-requirements/apply

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/receivables-audit-packages

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/receivables-audit-packages

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/receivables-audit-packages

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/receivables/invoices/import

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/receivables/invoices/import

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/receivables/invoices/import

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/settlements/{settlementId}/propose

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/settlements/{settlementId}/propose

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/settlements/{settlementId}/propose

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/test-copies/start

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/test-copies/start

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/test-copies/start

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/undo-groups/{groupId}/redo

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/undo-groups/{groupId}/redo

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/undo-groups/{groupId}/redo

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/undo-groups/{groupId}/undo

  • the `job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/undo-groups/{groupId}/undo

  • added the required property `job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/undo-groups/{groupId}/undo

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `packJob/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `200`

    GET /v1/vendor-privacy-requests/{requestId}

  • the `packJob/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `200`

    GET /v1/vendor-privacy-requests/{requestId}

  • added the required property `packJob/anyOf[#/components/schemas/Job]/result/anyOf[subschema #1]/kind` to the response with the `200` status

    GET /v1/vendor-privacy-requests/{requestId}

  • removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13, subschema #14, subschema #15, subschema #16, subschema #17, subschema #18, subschema #19, subschema #20` from the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response property `oneOf` list for the response status `202`

    POST /v1/warehouse/destinations/{destinationId}/backfill

  • the `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/` response's property `type` was narrowed from `any` to `object` for status `202`

    POST /v1/warehouse/destinations/{destinationId}/backfill

  • added the required property `anyOf[#/components/schemas/UndoAgentBatchResponse]/job/result/anyOf[subschema #1]/kind` to the response with the `202` status

    POST /v1/warehouse/destinations/{destinationId}/backfill

  • Breaking, accepted: replayProjection answers 202 job_started instead of 200: the replay is a PROJECTION_REPLAY job, because one claim of up to PROJECTION_REPLAY_MAX changes ran minutes under a 30 second request timeout. (ADR 0173, 2026-11-11; 1 findings over 1 operations)

  • Breaking, accepted: counterpartyEntity is an internal intercompany field that leaked into release 0001 (packages/contracts/src/receivables.ts, internalField); the customer answer no longer carries it. A redaction. (ADR 0173, 2026-11-11; 1 findings over 1 operations)

  • Breaking, accepted: counterpartyEntity is an internal intercompany field that leaked into release 0001 (packages/contracts/src/receivables.ts, internalField); the customer answer no longer carries it. A redaction. (ADR 0173, 2026-11-11; 1 findings over 1 operations)

  • Breaking, accepted: counterpartyEntity is an internal intercompany field that leaked into release 0001 (packages/contracts/src/receivables.ts, internalField); the customer answer no longer carries it. A redaction. (ADR 0173, 2026-11-11; 10 findings over 10 operations)

  • Breaking, accepted: createCustomer answers the customer shape, which lost counterpartyEntity, so the shared component it is made of is a new schema and is named afresh. The content is the one change above, not a second one. (ADR 0173, 2026-11-11; 1 findings over 1 operations)

Release 0001

2026-11-08

The first release: every operation is as in this document.

Told before it changes.

Book a demo and we show you how a deprecation reaches your integration.