Skip to main content
This page focuses on what you need while customizing UI. The complete canonical reference is React hooks.
This list is generated from the Velt SDK and is complete for what it covers: a name that isn’t listed here doesn’t exist; don’t guess names. Comment + notification + core hooks are documented in full; the remaining other-feature hooks are listed by name + return type + one-line purpose in “Other features (brief)” below.
The hooks you use to build custom UI (Headless) or to add data-driven extras alongside any approach. All from @veltdev/react. Types from @veltdev/types. Grouped by purpose: read (data/state you render), mutate (actions you call), events (callbacks), control (init/scope/imperative). This lists the commonly-used comment hooks plus a brief map of other features; the SDK exports many more hooks following the same naming, but everything you need for the customization patterns in these docs is here.

Read: data & state

Return shapes matter. Several read hooks return wrapper objects, not bare values (…Count*{ count }; useGetCommentAnnotations → a response object). Read the field, don’t render the object. When unsure of a return shape, console.log the hook’s value in your component to see it before rendering.

Mutate: actions

Most return an object with a function, e.g. const { addComment } = useAddComment(); then await addComment({ annotationId, comment }).

Events: callbacks

Control: init, scope, imperative


Imperative API via the client

Some controls aren’t hooks: call them on the comment element:
(These element APIs come from the typed comment element returned by client.getCommentElement().)

Other features (brief)

See Other features for how customization applies to these.

Other-feature hook exports

These are exported from @veltdev/react but belong to features outside the scope of these docs. They are listed here so the “a hook not listed doesn’t exist” rule holds: name, category, return type, and one-line purpose. Return types come from the SDK’s type definitions.