From 1d07b8c2d527edb7605f64d19fe600bc427b357a Mon Sep 17 00:00:00 2001 From: Mark Dennis Date: Thu, 8 Oct 2026 16:10:55 +0100 Subject: [PATCH 1/2] Align the 2.16 API reference across repositories - Add inbox_bulk_action to the activity log event types example and the activity_log activity_type enum. - Document the 200 response of GET /fin_voice/phone_number/{phone_number}. - Add the data property to ai_call_response. - Add the Server-Sent Events availability note to the Fin Agent tag. Co-Authored-By: Claude Opus 5.5 --- descriptions/2.16/api.intercom.io.yaml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index c14dbb34..56e51639 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 @@ -24034,6 +24042,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 +36636,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`.   From ba3cc4e3e180b1695a8ac135de52e7337bc2ad38 Mon Sep 17 00:00:00 2001 From: Mark Dennis Date: Mon, 12 Oct 2026 11:12:49 +0100 Subject: [PATCH 2/2] Describe the IP allowlist values of previous_state and new_state The activity log metadata fields previous_state and new_state also carry `enabled` or `disabled` for IP allowlist changes, not only `idle` or `occupied` for occupancy changes. Co-Authored-By: Claude Opus 5.5 --- descriptions/2.16/api.intercom.io.yaml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 56e51639..2c021def 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -23424,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