diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml
index c14dbb34..2c021def 100644
--- a/descriptions/2.16/api.intercom.io.yaml
+++ b/descriptions/2.16/api.intercom.io.yaml
@@ -830,6 +830,7 @@ paths:
                     - help_center_settings_change
                     - inbound_conversations_change
                     - inbox_access_change
+                    - inbox_bulk_action
                     - message_deletion
                     - message_state_change
                     - messenger_look_and_feel_change
@@ -22751,6 +22752,12 @@ paths:
           schema:
             type: string
       responses:
+        '200':
+          description: successful
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/ai_call_response"
         '401':
           description: Unauthorized
           content:
@@ -23267,6 +23274,7 @@ components:
           - help_center_settings_change
           - inbound_conversations_change
           - inbox_access_change
+          - inbox_bulk_action
           - macro_creation
           - macro_deletion
           - macro_update
@@ -23416,13 +23424,16 @@ components:
         previous_state:
           type: string
           nullable: true
-          description: The state before the change. `idle` or `occupied`, and null
-            when the Admin had not been classified yet.
+          description: The state before the change. `idle` or `occupied` for an
+            occupancy change, and null when the Admin had not been classified
+            yet; `enabled` or `disabled` for an IP allowlist change.
           example: idle
         new_state:
           type: string
           nullable: true
-          description: The state after the change. `idle` or `occupied`.
+          description: The state after the change. `idle` or `occupied` for an
+            occupancy change; `enabled` or `disabled` for an IP allowlist
+            change.
           example: occupied
         threshold_minutes:
           type: integer
@@ -24034,6 +24045,12 @@ components:
           items:
             type: object
           example: []
+        data:
+          type: object
+          description: The metadata object supplied when the call was registered, returned verbatim. Empty object when none was supplied.
+          example:
+            masterContactID: 'abc123'
+            DNIS: '+18005551212'
     app:
       title: App
       type: object
@@ -36622,6 +36639,12 @@ tags:
 
      
 
+    {% admonition type="warning" %}
+    Server-Sent Events (SSE) is available by application only. Contact your account team or Customer Support to request access.
+    {% /admonition %}
+
+     
+
     Integration centres on the Fin Agent API endpoints — start a conversation with `/fin/start` and continue it with `/fin/reply`, or drive Fin from your own agent with `/fin/capabilities`, `/fin/ask`, `/fin/procedures/{procedure_id}/run`, and `/fin/escalate` — plus a set of events that notify your application of Fin's status and responses. Events can be delivered via webhooks or Server-Sent Events (SSE). You can also record a customer satisfaction rating with `/fin/csat`.