Skip to content

Document websocket update success response format#900

Open
8bitpal wants to merge 2 commits into
mainfrom
fix/878-websocket-update-format
Open

Document websocket update success response format#900
8bitpal wants to merge 2 commits into
mainfrom
fix/878-websocket-update-format

Conversation

@8bitpal

@8bitpal 8bitpal commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

The /v2/updates subscribe page only showed the error variant of Either_JsCantonError_JsGetUpdatesResponse. The success format (JsGetUpdatesResponse) was completely absent.

Adds documentation of the success format above the existing error docs:

  • Shows the { "update": <Update> } wrapper
  • Lists all four Update variants (Transaction, OffsetCheckpoint, Reassignment, TopologyTransaction) in a table
  • Adds an example Transaction payload

Closes #878

…page

The auto-generated page only showed the error branch of the
Either_JsCantonError_JsGetUpdatesResponse oneOf. Adds the missing
success format (JsGetUpdatesResponse with its Update variants:
Transaction, OffsetCheckpoint, Reassignment, TopologyTransaction)
with an example JSON payload.

Closes #878

Signed-off-by: 8bitpal <eliashaase@gmail.com>
@mintlify

mintlify Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cantonfoundation 🟢 Ready View Preview Jun 29, 2026, 7:14 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Format of websocket streamed updates not documented?

1 participant