The Event Streaming migration guide and overview no longer describe moving off the legacy Streaming API (SAPI) as optional. Existing customers are automatically migrated to the Pulsar-based Event Streaming service on a rolling schedule, with advance notice sent ahead of each migration.
The Event Streaming field reference previously said boolean values in events "are represented as strings... rather than native JSON booleans" — a claim its own example immediately contradicted by showing both a quoted and an unquoted boolean value in the same payload. The section has been corrected and expanded to desc…
The Event Streaming field and event reference docs previously told integrators to use eventTS to calculate durations between lifecycle events — queue time, ring time, talk time, and wrap-up time. That was incorrect: eventTS is the time the interaction was first offered (queue entry), and it carries the identical value…
The Streaming API migration guide now documents a backwards-compatible adapter (Bridge) endpoint — a second migration path for existing Streaming API integrations that cannot move to the Pulsar API directly.