PATCH Conversations API Queue Transfer RoutingData Schema

Quick question about transferring a call to another queue programmatically using PATCH on the Conversations API.

My OpenTelemetry pipeline successfully traces the initial PATCH /api/v2/conversations/voice/{conversationId} request, yet the active session terminates instantly upon processing.

{"code":"badRequest","message":"RoutingData requires explicit queueId and priority."}

Which precise JSON structure should I inject into the routingData block to force a successful queue handoff?