Skip to content

Commit 2127e40

Browse files
committed
2.11 updates
1 parent 6b03761 commit 2127e40

File tree

1 file changed

+113
-27
lines changed

1 file changed

+113
-27
lines changed

descriptions/2.11/api.intercom.io.yaml

Lines changed: 113 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1363,7 +1363,7 @@ paths:
13631363

13641364
Companies are looked up via `company_id` in a `POST` request, if not found via `company_id`, the new company will be created, if found, that company will be updated.
13651365

1366-
{% admonition type="attention" name="Using `company_id`" %}
1366+
{% admonition type="warning" name="Using `company_id`" %}
13671367
You can set a unique `company_id` value when creating a company. However, it is not possible to update `company_id`. Be sure to set a unique value once upon creation of the company.
13681368
{% /admonition %}
13691369
responses:
@@ -1666,7 +1666,7 @@ paths:
16661666
description: |
16671667
You can update a single company using the Intercom provisioned `id`.
16681668

1669-
{% admonition type="attention" name="Using `company_id`" %}
1669+
{% admonition type="warning" name="Using `company_id`" %}
16701670
When updating a company it is not possible to update `company_id`. This can only be set once upon creation of the company.
16711671
{% /admonition %}
16721672
responses:
@@ -3716,7 +3716,6 @@ paths:
37163716
| email | String |
37173717
| email_domain | String |
37183718
| phone | String |
3719-
| formatted_phone | String |
37203719
| external_id | String |
37213720
| created_at | Date (UNIX Timestamp) |
37223721
| signed_up_at | Date (UNIX Timestamp) |
@@ -3754,7 +3753,7 @@ paths:
37543753

37553754
### Accepted Operators
37563755

3757-
{% admonition type="attention" name="Searching based on `created_at`" %}
3756+
{% admonition type="warning" name="Searching based on `created_at`" %}
37583757
You cannot use the `<=` or `>=` operators to search by `created_at`.
37593758
{% /admonition %}
37603759

@@ -4878,7 +4877,7 @@ paths:
48784877

48794878
### Accepted Fields
48804879

4881-
Most keys listed as part of the The conversation model is searchable, whether writeable or not. The value you search for has to match the accepted type, otherwise the query will fail (ie. as `created_at` accepts a date, the `value` cannot be a string such as `"foorbar"`).
4880+
Most keys listed in the table below are searchable, whether writeable or not. The value you search for has to match the accepted type, otherwise the query will fail (ie. as `created_at` accepts a date, the `value` cannot be a string such as `"foorbar"`).
48824881
The `source.body` field is unique as the search will not be performed against the entire value, but instead against every element of the value separately. For example, when searching for a conversation with a `"I need support"` body - the query should contain a `=` operator with the value `"support"` for such conversation to be returned. A query with a `=` operator and a `"need support"` value will not yield a result.
48834882

48844883
| Field | Type |
@@ -5816,8 +5815,11 @@ paths:
58165815
- Conversations
58175816
operationId: autoAssignConversation
58185817
description: |
5818+
{% admonition type="danger" name="Deprecation of Run Assignment Rules" %}
5819+
Run assignment rules is now deprecated in version 2.12 and future versions and will be permanently removed on December 31, 2026. After this date, any requests made to this endpoint will fail.
5820+
{% /admonition %}
58195821
You can let a conversation be automatically assigned following assignment rules.
5820-
{% admonition type="attention" name="When using workflows" %}
5822+
{% admonition type="warning" name="When using workflows" %}
58215823
It is not possible to use this endpoint with Workflows.
58225824
{% /admonition %}
58235825
responses:
@@ -5966,7 +5968,7 @@ paths:
59665968
description: |+
59675969
You can add participants who are contacts to a conversation, on behalf of either another contact or an admin.
59685970

5969-
{% admonition type="attention" name="Contacts without an email" %}
5971+
{% admonition type="warning" name="Contacts without an email" %}
59705972
If you add a contact via the email parameter and there is no user/lead found on that workspace with he given email, then we will create a new contact with `role` set to `lead`.
59715973
{% /admonition %}
59725974

@@ -6071,7 +6073,7 @@ paths:
60716073
description: |+
60726074
You can add participants who are contacts to a conversation, on behalf of either another contact or an admin.
60736075

6074-
{% admonition type="attention" name="Contacts without an email" %}
6076+
{% admonition type="warning" name="Contacts without an email" %}
60756077
If you add a contact via the email parameter and there is no user/lead found on that workspace with he given email, then we will create a new contact with `role` set to `lead`.
60766078
{% /admonition %}
60776079

@@ -10337,14 +10339,15 @@ paths:
1033710339
### Accepted Fields
1033810340

1033910341
Most keys listed as part of the Ticket model are searchable, whether writeable or not. The value you search for has to match the accepted type, otherwise the query will fail (ie. as `created_at` accepts a date, the `value` cannot be a string such as `"foobar"`).
10342+
The `description` field is unique as the search will not be performed against the entire value, but instead against every element of the value separately. For example, when searching for a conversation with a `"I need support"` description - the query should contain a `=` operator with the value `"support"` for such conversation to be returned. A query with a `=` operator and a `"need support"` value will not yield a result.
1034010343

1034110344
| Field | Type |
1034210345
| :---------------------------------------- | :--------------------------------------------------------------------------------------- |
1034310346
| id | String |
1034410347
| created_at | Date (UNIX timestamp) |
1034510348
| updated_at | Date (UNIX timestamp) |
10346-
| _default_title_ | String |
10347-
| _default_description_ | String |
10349+
| title | String |
10350+
| description | String |
1034810351
| category | String |
1034910352
| ticket_type_id | String |
1035010353
| contact_ids | String |
@@ -12757,6 +12760,11 @@ components:
1275712760
description: An object containing companies meta data about the companies that
1275812761
a contact has. Up to 10 will be displayed here. Use the url to get more.
1275912762
properties:
12763+
data:
12764+
type: array
12765+
description: An array of company data objects attached to the contact.
12766+
items:
12767+
"$ref": "#/components/schemas/company_data"
1276012768
url:
1276112769
type: string
1276212770
format: uri
@@ -12776,6 +12784,26 @@ components:
1277612784
- url
1277712785
- total_count
1277812786
- has_more
12787+
company_data:
12788+
title: Company Data
12789+
type: object
12790+
description: An object containing data about the companies that a contact is associated with.
12791+
properties:
12792+
id:
12793+
type: string
12794+
description: The unique identifier for the company which is given by Intercom.
12795+
example: 5ba682d23d7cf92bef87bfd4
12796+
type:
12797+
type: string
12798+
description: The type of the object
12799+
enum:
12800+
- company
12801+
example: company
12802+
url:
12803+
type: string
12804+
format: uri
12805+
description: The relative URL of the company.
12806+
example: "/companies/5ba682d23d7cf92bef87bfd4"
1277912807
contact_deleted:
1278012808
title: Contact Deleted
1278112809
type: object
@@ -12834,7 +12862,7 @@ components:
1283412862
contact_location:
1283512863
title: Contact Location
1283612864
type: object
12837-
description: An object containing location meta data about a Intercom contact.
12865+
description: An object containing location metadata about a Intercom contact.
1283812866
properties:
1283912867
type:
1284012868
type: string
@@ -13620,14 +13648,24 @@ components:
1362013648
conversation_source:
1362113649
title: Conversation source
1362213650
type: object
13623-
description: The Conversation Part that originated this conversation, which
13624-
can be Contact, Admin, Campaign, Automated or Operator initiated.
13651+
description: The type of the conversation part that started this conversation. Can be Contact, Admin, Campaign, Automated or Operator initiated.
1362513652
properties:
1362613653
type:
1362713654
type: string
1362813655
description: This includes conversation, email, facebook, instagram, phone_call,
1362913656
phone_switch, push, sms, twitter and whatsapp.
1363013657
example: conversation
13658+
enum:
13659+
- conversation
13660+
- email
13661+
- facebook
13662+
- instagram
13663+
- phone_call
13664+
- phone_switch
13665+
- push
13666+
- sms
13667+
- twitter
13668+
- whatsapp
1363113669
id:
1363213670
type: string
1363313671
description: The id representing the message.
@@ -15250,6 +15288,10 @@ components:
1525015288
- filesize
1525115289
- width
1525215290
- height
15291+
filter:
15292+
anyOf:
15293+
- "$ref": "#/components/schemas/single_filter_search_request"
15294+
- "$ref": "#/components/schemas/multiple_filter_search_request"
1525315295
group_content:
1525415296
title: Group Content
1525515297
type: object
@@ -15623,7 +15665,7 @@ components:
1562315665
- conversation_id
1562415666
multiple_filter_search_request:
1562515667
title: Multiple Filter Search Request
15626-
description: Search using Intercoms Search APIs with more than one filter.
15668+
description: Search with more than one filter.
1562715669
type: object
1562815670
properties:
1562915671
operator:
@@ -15634,17 +15676,10 @@ components:
1563415676
description: An operator to allow boolean inspection between multiple fields.
1563515677
example: AND
1563615678
value:
15637-
oneOf:
15638-
- type: array
15639-
description: Add mutiple filters.
15640-
title: multiple filter search request
15641-
items:
15642-
"$ref": "#/components/schemas/multiple_filter_search_request"
15643-
- type: array
15644-
description: Add a single filter field.
15645-
title: single filter search request
15646-
items:
15647-
"$ref": "#/components/schemas/single_filter_search_request"
15679+
type: array
15680+
items:
15681+
"$ref": "#/components/schemas/filter"
15682+
description: Nested filters or queries.
1564815683
news_item:
1564915684
title: News Item
1565015685
type: object
@@ -16270,7 +16305,51 @@ components:
1627016305
field:
1627116306
type: string
1627216307
description: The accepted field that you want to search on.
16273-
example: created_at
16308+
enum:
16309+
- id
16310+
- role
16311+
- name
16312+
- avatar
16313+
- owner_id
16314+
- email
16315+
- email_domain
16316+
- phone
16317+
- external_id
16318+
- created_at
16319+
- signed_up_at
16320+
- updated_at
16321+
- last_seen_at
16322+
- last_contacted_at
16323+
- last_replied_at
16324+
- last_email_opened_at
16325+
- last_email_clicked_at
16326+
- language_override
16327+
- browser
16328+
- browser_language
16329+
- os
16330+
- location.country
16331+
- location.city
16332+
- location.region
16333+
- unsubscribed_from_emails
16334+
- marked_email_as_spam
16335+
- has_hard_bounced
16336+
- ios_last_seen_at
16337+
- ios_app_version
16338+
- ios_device
16339+
- ios_app_device
16340+
- ios_os_version
16341+
- ios_app_name
16342+
- ios_sdk_version
16343+
- android_last_seen_at
16344+
- android_app_version
16345+
- android_device
16346+
- android_app_device
16347+
- android_app_name
16348+
- android_sdk_version
16349+
- segment_id
16350+
- tag_id
16351+
- custom_attributes.*
16352+
example: custom_attributes.favorite_color
1627416353
operator:
1627516354
type: string
1627616355
enum:
@@ -16288,7 +16367,14 @@ components:
1628816367
search for the value.
1628916368
example: ">"
1629016369
value:
16291-
type: string
16370+
oneOf:
16371+
- type: string
16372+
- type: integer
16373+
- type: array
16374+
items:
16375+
oneOf:
16376+
- type: string
16377+
- type: integer
1629216378
description: The value that you want to search on.
1629316379
example: '73732934'
1629416380
sla_applied:

0 commit comments

Comments
 (0)