From a3724e2b47ec3e1f42fda04cbb91d45eaa4a50f5 Mon Sep 17 00:00:00 2001
From: owenpearson <owen.pearson@ably.com>
Date: Tue, 5 May 2026 12:37:41 +0100
Subject: [PATCH] json-schemas: add `clientType` to client events connections

---
 json-schemas/src/client-events-connections.json | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/json-schemas/src/client-events-connections.json b/json-schemas/src/client-events-connections.json
index 94bd9497..5c688695 100644
--- a/json-schemas/src/client-events-connections.json
+++ b/json-schemas/src/client-events-connections.json
@@ -73,6 +73,11 @@
       "type": "string",
       "description": "The ID of the client that attempted the connection."
     },
+    "clientType": {
+      "type": "string",
+      "description": "Connection-level client type, one of 'user' or 'agent'. Set by the client via the clientType transport param at connection creation time, and immutable for the connection's lifetime.",
+      "enum": ["user", "agent"]
+    },
     "channels": {
       "type": "array",
       "description": "The list of channels referenced in the connection request. This is only relevant where channels are supported as part of the connection request, such as with SSE."