New: MCP server monitoring is live. Start free trial
LoopsSchemaBehavioral

Response schema changed for POST /v2/transactional/{transactionalId}/publish (TransactionalResponse)

Affected surface
POST /v2/transactional/{transactionalId}/publish
Affected field
TransactionalResponse

What changed

Response schema changed for POST /v2/transactional/{transactionalId}/publish (TransactionalResponse) Affected surface: POST /v2/transactional/{transactionalId}/publish. Root cause: schema `TransactionalResponse`. Detected at Wed, 03 Jun 2026 01:52:15 UTC UTC.

Diff

{
  "path": "POST /v2/transactional/{transactionalId}/publish",
  "removed_fields": [
    "success",
    "transactionalId"
  ],
  "schema_path": "schema TransactionalResponse"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.