Skip to content

Commit bbaac00

Browse files
authored
Remove Custom Channel Events API from all spec versions (#460)
1 parent 2906bde commit bbaac00

5 files changed

Lines changed: 0 additions & 906 deletions

File tree

descriptions/0/api.intercom.io.yaml

Lines changed: 0 additions & 290 deletions
Original file line numberDiff line numberDiff line change
@@ -10266,206 +10266,6 @@ paths:
1026610266
message: Requested resource is not available in current API version.
1026710267
schema:
1026810268
"$ref": "#/components/schemas/error"
10269-
"/custom_channel_events/notify_new_conversation":
10270-
post:
10271-
summary: Notify Intercom of a new conversation created in a custom channel
10272-
tags:
10273-
- Custom Channel Events
10274-
operationId: notifyNewConversation
10275-
description: |
10276-
Notifies Intercom that a new conversation was created in your custom channel/platform. This triggers conversation creation and workflow automations within Intercom for your custom channel integration.
10277-
> **Note:** This endpoint is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.
10278-
parameters:
10279-
- name: Intercom-Version
10280-
in: header
10281-
required: true
10282-
schema:
10283-
$ref: '#/components/schemas/intercom_version_preview'
10284-
requestBody:
10285-
required: true
10286-
content:
10287-
application/json:
10288-
schema:
10289-
$ref: '#/components/schemas/custom_channel_base_event'
10290-
examples:
10291-
example-1:
10292-
summary: Example request
10293-
value:
10294-
event_id: "evt_12345"
10295-
external_conversation_id: "conv_67890"
10296-
contact:
10297-
type: "user"
10298-
external_id: "user_001"
10299-
name: "Jane Doe"
10300-
email: "jane.doe@example.com"
10301-
responses:
10302-
'200':
10303-
$ref: '#/components/responses/CustomChannelNotificationSuccess'
10304-
'400':
10305-
$ref: '#/components/responses/BadRequest'
10306-
'401':
10307-
$ref: "#/components/responses/Unauthorized"
10308-
'404':
10309-
$ref: '#/components/responses/ObjectNotFound'
10310-
'422':
10311-
$ref: '#/components/responses/ValidationError'
10312-
"/custom_channel_events/notify_new_message":
10313-
post:
10314-
summary: Notify Intercom of a new message in a custom channel conversation
10315-
tags:
10316-
- Custom Channel Events
10317-
operationId: notifyNewMessage
10318-
description: |
10319-
Notifies Intercom that a new message was sent in a conversation on your custom channel/platform. This allows Intercom to process the message and trigger any relevant workflow automations.
10320-
> **Note:** This endpoint is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.
10321-
parameters:
10322-
- name: Intercom-Version
10323-
in: header
10324-
required: true
10325-
schema:
10326-
$ref: '#/components/schemas/intercom_version_preview'
10327-
requestBody:
10328-
required: true
10329-
content:
10330-
application/json:
10331-
schema:
10332-
allOf:
10333-
- $ref: '#/components/schemas/custom_channel_base_event'
10334-
- type: object
10335-
properties:
10336-
body:
10337-
type: string
10338-
description: The message content sent by the user.
10339-
required:
10340-
- body
10341-
examples:
10342-
example-1:
10343-
summary: Example request
10344-
value:
10345-
event_id: "evt_54321"
10346-
external_conversation_id: "conv_98765"
10347-
contact:
10348-
type: "user"
10349-
external_id: "user_002"
10350-
name: "John Smith"
10351-
email: "john.smith@example.com"
10352-
body: "Hello, I need help with my order."
10353-
responses:
10354-
'200':
10355-
$ref: '#/components/responses/CustomChannelNotificationSuccess'
10356-
'400':
10357-
$ref: '#/components/responses/BadRequest'
10358-
'401':
10359-
$ref: "#/components/responses/Unauthorized"
10360-
'404':
10361-
$ref: '#/components/responses/ObjectNotFound'
10362-
'422':
10363-
$ref: '#/components/responses/ValidationError'
10364-
"/custom_channel_events/notify_quick_reply_selected":
10365-
post:
10366-
summary: Notify Intercom of a quick reply response in a custom channel conversation
10367-
tags:
10368-
- Custom Channel Events
10369-
operationId: notifyQuickReplySelected
10370-
description: |
10371-
Notifies Intercom that a user selected a quick reply option in your custom channel/platform. This allows Intercom to process the response and trigger any relevant workflow automations.
10372-
> **Note:** This endpoint is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.
10373-
parameters:
10374-
- name: Intercom-Version
10375-
in: header
10376-
required: true
10377-
schema:
10378-
$ref: '#/components/schemas/intercom_version_preview'
10379-
requestBody:
10380-
required: true
10381-
content:
10382-
application/json:
10383-
schema:
10384-
allOf:
10385-
- $ref: '#/components/schemas/custom_channel_base_event'
10386-
- type: object
10387-
properties:
10388-
quick_reply_option_id:
10389-
type: string
10390-
description: Id of the selected quick reply option.
10391-
required:
10392-
- quick_reply_option_id
10393-
examples:
10394-
example-1:
10395-
summary: Example request
10396-
value:
10397-
event_id: "evt_67890"
10398-
external_conversation_id: "conv_13579"
10399-
contact:
10400-
type: "user"
10401-
external_id: "user_003"
10402-
name: "Alice Example"
10403-
email: "alice@example.com"
10404-
quick_reply_option_id: "1234"
10405-
responses:
10406-
'200':
10407-
$ref: '#/components/responses/CustomChannelNotificationSuccess'
10408-
'400':
10409-
$ref: '#/components/responses/BadRequest'
10410-
'401':
10411-
$ref: "#/components/responses/Unauthorized"
10412-
'404':
10413-
$ref: '#/components/responses/ObjectNotFound'
10414-
'422':
10415-
$ref: '#/components/responses/ValidationError'
10416-
"/custom_channel_events/notify_attribute_collected":
10417-
post:
10418-
summary: Notify Intercom of an attribute collector response in a custom channel conversation
10419-
tags:
10420-
- Custom Channel Events
10421-
operationId: notifyAttributeCollected
10422-
description: |
10423-
Notifies Intercom that a user provided a response to an attribute collector in your custom channel/platform. This allows Intercom to process the attribute and trigger any relevant workflow automations.
10424-
> **Note:** This endpoint is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.
10425-
parameters:
10426-
- name: Intercom-Version
10427-
in: header
10428-
required: true
10429-
schema:
10430-
$ref: '#/components/schemas/intercom_version_preview'
10431-
requestBody:
10432-
required: true
10433-
content:
10434-
application/json:
10435-
schema:
10436-
allOf:
10437-
- $ref: '#/components/schemas/custom_channel_base_event'
10438-
- type: object
10439-
properties:
10440-
attribute:
10441-
$ref: '#/components/schemas/custom_channel_attribute'
10442-
required:
10443-
- attribute
10444-
examples:
10445-
example-1:
10446-
summary: Example request
10447-
value:
10448-
event_id: "evt_24680"
10449-
external_conversation_id: "conv_11223"
10450-
contact:
10451-
type: "user"
10452-
external_id: "user_004"
10453-
name: "Bob Example"
10454-
email: "bob@example.com"
10455-
attribute:
10456-
id: "shipping_address"
10457-
value: "123 Main St, Springfield"
10458-
responses:
10459-
'200':
10460-
$ref: '#/components/responses/CustomChannelNotificationSuccess'
10461-
'400':
10462-
$ref: '#/components/responses/BadRequest'
10463-
'401':
10464-
$ref: "#/components/responses/Unauthorized"
10465-
'404':
10466-
$ref: '#/components/responses/ObjectNotFound'
10467-
'422':
10468-
$ref: '#/components/responses/ValidationError'
1046910269
"/custom_object_instances/{custom_object_type_identifier}":
1047010270
parameters:
1047110271
- name: custom_object_type_identifier
@@ -24860,76 +24660,6 @@ components:
2486024660
type: string
2486124661
description: Name of the action
2486224662
example: Jira Create Issue
24863-
custom_channel_attribute:
24864-
title: Custom Channel - Attribute
24865-
type: object
24866-
required:
24867-
- id
24868-
- value
24869-
properties:
24870-
id:
24871-
type: string
24872-
description: Identifier for the attribute being collected.
24873-
value:
24874-
type: string
24875-
description: Value provided by the user for the attribute.
24876-
custom_channel_base_event:
24877-
title: Custom Channel - Base Event
24878-
type: object
24879-
properties:
24880-
event_id:
24881-
type: string
24882-
description: Unique identifier for the event.
24883-
external_conversation_id:
24884-
type: string
24885-
description: Identifier for the conversation in your application.
24886-
contact:
24887-
$ref: '#/components/schemas/custom_channel_contact'
24888-
required:
24889-
- event_id
24890-
- external_conversation_id
24891-
- contact
24892-
custom_channel_contact:
24893-
title: Custom Channel - Simplified Contact
24894-
type: object
24895-
required:
24896-
- type
24897-
- external_id
24898-
properties:
24899-
type:
24900-
type: string
24901-
enum: [user, lead]
24902-
description: Type of contact, must be "user" or "lead".
24903-
external_id:
24904-
type: string
24905-
description: External identifier for the contact. Intercom will take care of the mapping of your external_id with our internal ones so you don't have to worry about it.
24906-
name:
24907-
type: string
24908-
description: Name of the contact. Required for user type.
24909-
email:
24910-
type: string
24911-
format: email
24912-
description: Email address of the contact. Required for user type.
24913-
custom_channel_notification_response:
24914-
type: object
24915-
required:
24916-
- external_conversation_id
24917-
- conversation_id
24918-
- external_contact_id
24919-
- contact_id
24920-
properties:
24921-
external_conversation_id:
24922-
type: string
24923-
description: The external conversation ID provided in the notification request
24924-
conversation_id:
24925-
type: string
24926-
description: The Intercom conversation ID mapped to the external conversation ID
24927-
external_contact_id:
24928-
type: string
24929-
description: The external contact ID provided in the notification request
24930-
contact_id:
24931-
type: string
24932-
description: The Intercom contact ID mapped to the external contact ID
2493324663
custom_action_finished:
2493424664
title: Part type - custom_action_finished
2493524665
type: object
@@ -29404,19 +29134,6 @@ components:
2940429134
message: Contact not found or could not be created
2940529135
schema:
2940629136
"$ref": "#/components/schemas/error"
29407-
CustomChannelNotificationSuccess:
29408-
description: Successfully notified Intercom
29409-
content:
29410-
application/json:
29411-
schema:
29412-
$ref: '#/components/schemas/custom_channel_notification_response'
29413-
examples:
29414-
NotificationSuccess:
29415-
value:
29416-
external_conversation_id: "customer_conversation_id_12"
29417-
conversation_id: "intercom_conversation_id_34"
29418-
external_contact_id: "customer_contact_id_56"
29419-
contact_id: "intercom_contact_id_79"
2942029137
servers:
2942129138
- url: https://api.intercom.io
2942229139
description: The production API server
@@ -29463,13 +29180,6 @@ tags:
2946329180
externalDocs:
2946429181
description: What is a conversation?
2946529182
url: https://www.intercom.com/help/en/articles/4323904-what-is-a-conversation
29466-
- name: Custom Channel Events
29467-
description: |
29468-
With the "Custom Channel" integration, you can bring Fin and Intercom capabilities to your own platform via API, enabling powerful custom integrations.
29469-
29470-
Intercom treats your integration like any other Intercom channel, allowing your application and Intercom to exchange events seamlessly. This makes it possible, for example, for your users to interact with Fin directly within your own application’s UI.
29471-
29472-
> **Note:** "Fin over API" is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.
2947329183
- name: Custom Object Instances
2947429184
description: |
2947529185
Everything about your Custom Object instances.

0 commit comments

Comments
 (0)