You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
1368
1368
{% /admonition %}
1369
1369
responses:
@@ -1666,7 +1666,7 @@ paths:
1666
1666
description: |
1667
1667
You can update a single company using the Intercom provisioned `id`.
When updating a company it is not possible to update `company_id`. This can only be set once upon creation of the company.
1671
1671
{% /admonition %}
1672
1672
responses:
@@ -3716,7 +3716,6 @@ paths:
3716
3716
| email | String |
3717
3717
| email_domain | String |
3718
3718
| phone | String |
3719
-
| formatted_phone | String |
3720
3719
| external_id | String |
3721
3720
| created_at | Date (UNIX Timestamp) |
3722
3721
| signed_up_at | Date (UNIX Timestamp) |
@@ -3754,7 +3753,7 @@ paths:
3754
3753
3755
3754
### Accepted Operators
3756
3755
3757
-
{% admonition type="attention" name="Searching based on `created_at`" %}
3756
+
{% admonition type="warning" name="Searching based on `created_at`" %}
3758
3757
You cannot use the `<=` or `>=` operators to search by `created_at`.
3759
3758
{% /admonition %}
3760
3759
@@ -4878,7 +4877,7 @@ paths:
4878
4877
4879
4878
### Accepted Fields
4880
4879
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"`).
4882
4881
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.
4883
4882
4884
4883
| Field | Type |
@@ -5816,8 +5815,11 @@ paths:
5816
5815
- Conversations
5817
5816
operationId: autoAssignConversation
5818
5817
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 %}
5819
5821
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" %}
5821
5823
It is not possible to use this endpoint with Workflows.
5822
5824
{% /admonition %}
5823
5825
responses:
@@ -5966,7 +5968,7 @@ paths:
5966
5968
description: |+
5967
5969
You can add participants who are contacts to a conversation, on behalf of either another contact or an admin.
5968
5970
5969
-
{% admonition type="attention" name="Contacts without an email" %}
5971
+
{% admonition type="warning" name="Contacts without an email" %}
5970
5972
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`.
5971
5973
{% /admonition %}
5972
5974
@@ -6071,7 +6073,7 @@ paths:
6071
6073
description: |+
6072
6074
You can add participants who are contacts to a conversation, on behalf of either another contact or an admin.
6073
6075
6074
-
{% admonition type="attention" name="Contacts without an email" %}
6076
+
{% admonition type="warning" name="Contacts without an email" %}
6075
6077
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`.
6076
6078
{% /admonition %}
6077
6079
@@ -10337,14 +10339,15 @@ paths:
10337
10339
### Accepted Fields
10338
10340
10339
10341
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.
0 commit comments