From 349cbbb9197aafc282b5beaec43de90400d4113c Mon Sep 17 00:00:00 2001 From: Rahul D'Souza Date: Thu, 16 Apr 2026 11:20:14 +0100 Subject: [PATCH] Regenerate Postman collections for v2.7-2.13 to sync with spec changes Collections were last bulk-generated in PR #302 (Sep 2025) and have since drifted from the specs. Changes include display_avatar query param additions, descriptive path parameter names (from #306), and updated examples. Co-Authored-By: Claude Opus 4.6 --- postman/2.10/README.md | 2 +- .../2.10/intercom-api.postman_collection.json | 22 +++++++++------ postman/2.11/README.md | 2 +- .../2.11/intercom-api.postman_collection.json | 20 ++++++++----- postman/2.12/README.md | 2 +- .../2.12/intercom-api.postman_collection.json | 28 +++++++++++-------- postman/2.13/README.md | 2 +- .../2.13/intercom-api.postman_collection.json | 28 +++++++++++-------- postman/2.7/README.md | 2 +- .../2.7/intercom-api.postman_collection.json | 16 +++++++---- postman/2.8/README.md | 2 +- .../2.8/intercom-api.postman_collection.json | 16 +++++++---- postman/2.9/README.md | 2 +- .../2.9/intercom-api.postman_collection.json | 20 ++++++++----- 14 files changed, 103 insertions(+), 61 deletions(-) diff --git a/postman/2.10/README.md b/postman/2.10/README.md index abda089..0481ef9 100644 --- a/postman/2.10/README.md +++ b/postman/2.10/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.10. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:41.870Z +Last updated: 2026-04-16T10:19:17.948Z diff --git a/postman/2.10/intercom-api.postman_collection.json b/postman/2.10/intercom-api.postman_collection.json index 4403283..7ffe111 100644 --- a/postman/2.10/intercom-api.postman_collection.json +++ b/postman/2.10/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:41.867Z" + "updatedAt": "2026-04-16T10:19:17.947Z" }, "item": [ { @@ -149,7 +149,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -2018,7 +2024,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -2478,7 +2484,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\"\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\"\n}", "urlencoded": [], "formdata": [] } @@ -6654,7 +6660,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom." + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -6758,7 +6764,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ]\n}", + "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ],\n \"cross_post\": true\n}", "urlencoded": [], "formdata": [] } @@ -6914,7 +6920,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom" + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -7161,7 +7167,7 @@ "event": [], "variable": [ { - "id": "38750aec-1917-4f4c-945c-2d4a64fa1c50", + "id": "775cd593-a628-4686-bc6b-6e94bc538ec0", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.11/README.md b/postman/2.11/README.md index 5f8a3dd..1c803f0 100644 --- a/postman/2.11/README.md +++ b/postman/2.11/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.11. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.038Z +Last updated: 2026-04-16T10:19:18.108Z diff --git a/postman/2.11/intercom-api.postman_collection.json b/postman/2.11/intercom-api.postman_collection.json index 96ee838..467462b 100644 --- a/postman/2.11/intercom-api.postman_collection.json +++ b/postman/2.11/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.036Z" + "updatedAt": "2026-04-16T10:19:18.107Z" }, "item": [ { @@ -149,7 +149,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -2067,7 +2073,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -2527,7 +2533,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"created_at\": 1671028894\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\",\n \"created_at\": 1671028894\n}", "urlencoded": [], "formdata": [] } @@ -6845,7 +6851,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ]\n}", + "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ],\n \"cross_post\": true\n}", "urlencoded": [], "formdata": [] } @@ -6955,7 +6961,7 @@ ] }, "method": "POST", - "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| _default_title_ | String |\n| _default_description_ | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", + "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| title | String |\n| description | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", "header": [ { "key": "Intercom-Version", @@ -7248,7 +7254,7 @@ "event": [], "variable": [ { - "id": "109a9146-30eb-4db4-9c86-f5a964012fda", + "id": "00f9b4cd-76db-4fe4-98a9-02ff212931e8", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.12/README.md b/postman/2.12/README.md index 6f09d47..a42811a 100644 --- a/postman/2.12/README.md +++ b/postman/2.12/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.12. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.191Z +Last updated: 2026-04-16T10:19:18.262Z diff --git a/postman/2.12/intercom-api.postman_collection.json b/postman/2.12/intercom-api.postman_collection.json index 41498dc..d917b11 100644 --- a/postman/2.12/intercom-api.postman_collection.json +++ b/postman/2.12/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.189Z" + "updatedAt": "2026-04-16T10:19:18.260Z" }, "item": [ { @@ -745,7 +745,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -2614,7 +2620,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -3074,7 +3080,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"created_at\": 1671028894\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\",\n \"created_at\": 1671028894\n}", "urlencoded": [], "formdata": [] } @@ -3567,7 +3573,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"read\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"read\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 9,\n \"start_date_iso8601\": \"2023-03-04T09:46:14Z\",\n \"end_date_timestamp\": 1677923174\n }\n}", "urlencoded": [], "formdata": [] } @@ -5925,7 +5931,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"phone\": \"+1 1234567890\",\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"phone\": \"+1 1234567890\",\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 9,\n \"start_date_iso8601\": \"2023-03-04T09:46:14Z\",\n \"end_date_timestamp\": 1677923174\n }\n}", "urlencoded": [], "formdata": [] } @@ -7246,7 +7252,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom." + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -7350,7 +7356,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ]\n}", + "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ],\n \"cross_post\": true\n}", "urlencoded": [], "formdata": [] } @@ -7460,7 +7466,7 @@ ] }, "method": "POST", - "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\nThe `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.\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| _default_title_ | String |\n| _default_description_ | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", + "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\nThe `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.\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| title | String |\n| description | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", "header": [ { "key": "Intercom-Version", @@ -7506,7 +7512,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom" + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -7753,7 +7759,7 @@ "event": [], "variable": [ { - "id": "8ba2d811-73b8-4785-a0a9-e256111d5e3f", + "id": "cd0d0e08-928c-42ad-adc3-87e39e1204e6", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.13/README.md b/postman/2.13/README.md index e8055c8..cf77d25 100644 --- a/postman/2.13/README.md +++ b/postman/2.13/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.13. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.346Z +Last updated: 2026-04-16T10:19:18.422Z diff --git a/postman/2.13/intercom-api.postman_collection.json b/postman/2.13/intercom-api.postman_collection.json index 56cb515..84e00f8 100644 --- a/postman/2.13/intercom-api.postman_collection.json +++ b/postman/2.13/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.343Z" + "updatedAt": "2026-04-16T10:19:18.421Z" }, "item": [ { @@ -745,7 +745,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -2677,7 +2683,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -3201,7 +3207,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"created_at\": 1671028894\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\",\n \"created_at\": 1671028894\n}", "urlencoded": [], "formdata": [] } @@ -3749,7 +3755,7 @@ ] }, "method": "DELETE", - "description": "You can delete a single conversation.", + "description": "{% admonition type=\"warning\" name=\"Irreversible operation\" %}\nDeleting a conversation is permanent and cannot be reversed.\n{% /admonition %}\n\nDeleting a conversation permanently removes it from the inbox. All sensitive data is deleted, including admin and user replies, conversation attributes, uploads, and related content. The conversation will still appear in reporting, though some data may be incomplete due to the deletion.\n", "header": [ { "key": "Intercom-Version", @@ -8129,7 +8135,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom." + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -8233,7 +8239,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ]\n}", + "raw": "{\n \"message_type\": \"comment\",\n \"type\": \"admin\",\n \"body\": \"Hello there!\",\n \"created_at\": 1590000000,\n \"attachment_urls\": \"\",\n \"admin_id\": \"3156780\",\n \"reply_options\": [\n {\n \"text\": \"\",\n \"uuid\": \"\"\n }\n ],\n \"cross_post\": true\n}", "urlencoded": [], "formdata": [] } @@ -8343,7 +8349,7 @@ ] }, "method": "POST", - "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\nThe `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.\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| _default_title_ | String |\n| _default_description_ | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", + "description": "You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want.\n\nTo search for tickets, you send a `POST` request to `https://api.intercom.io/tickets/search`.\n\nThis will accept a query object in the body which will define your filters.\n{% admonition type=\"warning\" name=\"Optimizing search queries\" %}\n Search queries can be complex, so optimizing them can help the performance of your search.\n Use the `AND` and `OR` operators to combine multiple filters to get the exact results you need and utilize\n pagination to limit the number of results returned. The default is `20` results per page.\n See the [pagination section](https://developers.intercom.com/docs/build-an-integration/learn-more/rest-apis/pagination/#example-search-conversations-request) for more details on how to use the `starting_after` param.\n{% /admonition %}\n\n### Nesting & Limitations\n\nYou can nest these filters in order to get even more granular insights that pinpoint exactly what you need. Example: (1 OR 2) AND (3 OR 4).\nThere are some limitations to the amount of multiples there can be:\n- There's a limit of max 2 nested filters\n- There's a limit of max 15 filters for each AND or OR group\n\n### Accepted Fields\n\nMost 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\"`).\nThe `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.\n\n| Field | Type |\n| :---------------------------------------- | :--------------------------------------------------------------------------------------- |\n| id | String |\n| created_at | Date (UNIX timestamp) |\n| updated_at | Date (UNIX timestamp) |\n| title | String |\n| description | String |\n| category | String |\n| ticket_type_id | String |\n| contact_ids | String |\n| teammate_ids | String |\n| admin_assignee_id | String |\n| team_assignee_id | String |\n| open | Boolean |\n| state | String |\n| snoozed_until | Date (UNIX timestamp) |\n| ticket_attribute.{id} | String or Boolean or Date (UNIX timestamp) or Float or Integer |\n\n### Accepted Operators\n\n{% admonition type=\"info\" name=\"Searching based on `created_at`\" %}\n You may use the `<=` or `>=` operators to search by `created_at`.\n{% /admonition %}\n\nThe table below shows the operators you can use to define how you want to search for the value. The operator should be put in as a string (`\"=\"`). The operator has to be compatible with the field's type (eg. you cannot search with `>` for a given string value as it's only compatible for integer's and dates).\n\n| Operator | Valid Types | Description |\n| :------- | :----------------------------- | :----------------------------------------------------------- |\n| = | All | Equals |\n| != | All | Doesn't Equal |\n| IN | All | In Shortcut for `OR` queries Values most be in Array |\n| NIN | All | Not In Shortcut for `OR !` queries Values must be in Array |\n| > | Integer Date (UNIX Timestamp) | Greater (or equal) than |\n| < | Integer Date (UNIX Timestamp) | Lower (or equal) than |\n| ~ | String | Contains |\n| !~ | String | Doesn't Contain |\n| ^ | String | Starts With |\n| $ | String | Ends With |\n", "header": [ { "key": "Intercom-Version", @@ -8389,7 +8395,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom" + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -8485,7 +8491,7 @@ ] }, "method": "DELETE", - "description": "You can delete a ticket using the Intercom provided ID.", + "description": "{% admonition type=\"warning\" name=\"Irreversible operation\" %}\nDeleting a ticket is permanent and cannot be reversed.\n{% /admonition %}\n\nDeleting a ticket permanently removes it from the inbox. All sensitive data is deleted, including admin and user replies, ticket attributes, uploads, and related content. The ticket will still appear in reporting, though some data may be incomplete due to the deletion.\n", "header": [ { "key": "Intercom-Version", @@ -8698,7 +8704,7 @@ "event": [], "variable": [ { - "id": "238e0ce0-eb64-42bf-9abe-dd99a9b88e5b", + "id": "16f863d6-5be9-4fb1-9474-7a735175bcdb", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.7/README.md b/postman/2.7/README.md index a23d6b5..df492ef 100644 --- a/postman/2.7/README.md +++ b/postman/2.7/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.7. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.648Z +Last updated: 2026-04-16T10:19:18.925Z diff --git a/postman/2.7/intercom-api.postman_collection.json b/postman/2.7/intercom-api.postman_collection.json index 200c15f..e51bf55 100644 --- a/postman/2.7/intercom-api.postman_collection.json +++ b/postman/2.7/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.646Z" + "updatedAt": "2026-04-16T10:19:18.924Z" }, "item": [ { @@ -149,7 +149,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -1942,7 +1948,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -2402,7 +2408,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\"\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\"\n}", "urlencoded": [], "formdata": [] } @@ -6430,7 +6436,7 @@ "event": [], "variable": [ { - "id": "1741355c-0400-4917-8f42-5ceb2bff758a", + "id": "58ba2f28-06be-4079-a82d-88df56a2e810", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.8/README.md b/postman/2.8/README.md index c112aba..518ca62 100644 --- a/postman/2.8/README.md +++ b/postman/2.8/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.8. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.763Z +Last updated: 2026-04-16T10:19:19.046Z diff --git a/postman/2.8/intercom-api.postman_collection.json b/postman/2.8/intercom-api.postman_collection.json index e0c89d2..f7a256c 100644 --- a/postman/2.8/intercom-api.postman_collection.json +++ b/postman/2.8/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.761Z" + "updatedAt": "2026-04-16T10:19:19.045Z" }, "item": [ { @@ -149,7 +149,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -1942,7 +1948,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -2402,7 +2408,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\"\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\"\n}", "urlencoded": [], "formdata": [] } @@ -6430,7 +6436,7 @@ "event": [], "variable": [ { - "id": "dc34d678-d394-4c40-be69-84cd09b5c7d1", + "id": "b3b7fa94-3108-4e0d-a67d-1a0be24c7ad1", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string", diff --git a/postman/2.9/README.md b/postman/2.9/README.md index fc2cec4..39b5068 100644 --- a/postman/2.9/README.md +++ b/postman/2.9/README.md @@ -12,4 +12,4 @@ This directory contains the Postman collection for Intercom API version 2.9. 3. Set your access token in the environment variables 4. Start making API calls! -Last updated: 2025-08-27T09:13:42.902Z +Last updated: 2026-04-16T10:19:19.181Z diff --git a/postman/2.9/intercom-api.postman_collection.json b/postman/2.9/intercom-api.postman_collection.json index e61ed37..0035a57 100644 --- a/postman/2.9/intercom-api.postman_collection.json +++ b/postman/2.9/intercom-api.postman_collection.json @@ -8,7 +8,7 @@ "url": "https://developers.intercom.com" }, "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json", - "updatedAt": "2025-08-27T09:13:42.899Z" + "updatedAt": "2026-04-16T10:19:19.180Z" }, "item": [ { @@ -149,7 +149,13 @@ "path": [ "admins" ], - "query": [], + "query": [ + { + "key": "display_avatar", + "value": "true", + "description": "If set to true, the response will include the admin's avatar object containing the image URL. Defaults to false." + } + ], "variable": [] }, "auth": { @@ -1942,7 +1948,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"role\": \"\",\n \"external_id\": \"\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": \"\"\n}", + "raw": "{\n \"role\": \"user\",\n \"external_id\": \"625e90fc55ab113b6d92175f\",\n \"email\": \"jdoe@example.com\",\n \"phone\": \"+353871234567\",\n \"name\": \"John Doe\",\n \"avatar\": \"https://www.example.com/avatar_image.jpg\",\n \"signed_up_at\": 1571672154,\n \"last_seen_at\": 1571672154,\n \"owner_id\": 123,\n \"unsubscribed_from_emails\": true,\n \"custom_attributes\": {\n \"paid_subscriber\": true,\n \"monthly_spend\": 155.5,\n \"team_mates\": 1\n }\n}", "urlencoded": [], "formdata": [] } @@ -2402,7 +2408,7 @@ ], "body": { "mode": "raw", - "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\"\n}", + "raw": "{\n \"from\": {\n \"type\": \"user\",\n \"id\": \"536e564f316c83104c000020\"\n },\n \"body\": \"Hello\",\n \"subject\": \"Thanks for everything\",\n \"attachment_urls\": \"\"\n}", "urlencoded": [], "formdata": [] } @@ -6670,7 +6676,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom." + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -6866,7 +6872,7 @@ "key": "id", "value": "id", "disabled": false, - "description": "The unique identifier for the ticket which is given by Intercom" + "description": "The unique identifier for the ticket which is given by Intercom.\n{% admonition type=\"info\" name=\"Not the Inbox ticket ID\" %}\nThis is the internal `id` field from the API response, not the `ticket_id` displayed in the Intercom Inbox (e.g., #12345). Use the `id` value from the ticket object returned by the API.\n{% /admonition %}\n" } ] }, @@ -7113,7 +7119,7 @@ "event": [], "variable": [ { - "id": "3f7b05f8-29ba-4f03-9827-c7dba593369f", + "id": "612dc35d-349e-4cd3-8fca-292ee0ecd089", "key": "bearerToken", "value": "{{bearerToken}}", "type": "string",