# Intercom API

The intercom API reference.

Version: Preview
License: MIT

## Servers

The production API server
```
https://api.intercom.io
```

The european API server
```
https://api.eu.intercom.io
```

The australian API server
```
https://api.au.intercom.io
```

## Security

### bearerAuth

Type: http
Scheme: bearer

## Download OpenAPI description

 - [Intercom API](https://developers.intercom.com/_bundle/docs/references/@Preview/rest-api/api.intercom.io.yaml)

## Admins

 - [Teammate Office Hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/admin_office_hours.md): Schema: #/components/schemas/admin_office_hours
 - [Activity Log Event Types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/activity_log_event_type_list.md): Schema: #/components/schemas/activity_log_event_type_list
 - [Admin](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/admin.md): Schema: #/components/schemas/admin
 - [GET /me](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/identifyadmin.md): You can view the currently authorised admin along with the embedded app object (a "workspace" in legacy terminology). > 🚧 Single Sign On If you are building a custom "Log in with Intercom" flow for y
 - [PUT /admins/{id}/away](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/setawayadmin.md): You can set an Admin as away for the Inbox. When `away_mode_reassign` is `true`, the request can return a `403` if the teammate does not have Inbox access. Requires the `update_admins` OAuth scope.
 - [GET /admins/activity_logs](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/listactivitylogs.md): You can get a log of activities by all admins in an app. Requires the `read_admins` OAuth scope.
 - [POST /admins/activity_logs/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/searchactivitylogs.md): Search and filter admin activity logs using a POST request with event type filter in the request body. You can find more details about the available event types in the List all activity log event type
 - [GET /admins/activity_log_event_types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/listactivitylogeventtypes.md): You can get a list of all activity log event types. This is useful for discovering valid values to use with the `event_types` filter on the Search activity logs endpoint. Requires the `read_admins` OA
 - [GET /admins](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/listadmins.md): You can fetch a list of admins for a given workspace. Requires the `read_admins` OAuth scope.
 - [GET /admins/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/listadminofficehours.md): You can list teammates who have their own office hours schedule. Teammates who inherit office hours are not included. Results include only teammates you can access. Use `pages.next.starting_after` to
 - [PUT /admins/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/bulkupdateadminofficehours.md): You can assign or clear office hours schedules for up to 50 teammates in one request. Send a non-empty `assignments` array, with each teammate listed at most once. Each teammate and each non-null sche
 - [GET /admins/{id}/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/retrieveadminofficehours.md): You can retrieve a teammate's own office hours schedule assignment. An `office_hours_schedule_id` of `null` means the teammate has no schedule of their own and inherits office hours instead. This endp
 - [PUT /admins/{id}/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/updateadminofficehours.md): You can assign an office hours schedule to a teammate or set `office_hours_schedule_id` to `null` to remove their own schedule so they inherit office hours. The field is required, even when its value
 - [GET /admins/find_by_email](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/findadminbyemail.md): You can find an admin in your workspace by their email address. The response is the same as retrieving the admin by id. Requires the `read_admins` OAuth scope.
 - [GET /admins/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/retrieveadmin.md): You can retrieve the details of a single admin. Requires the `read_single_admin` or `read_admins` OAuth scope.
 - [DELETE /admins/remove](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/admins/removeadmin.md): You can remove a single admin (teammate) from your workspace. Requires the `remove_admins` OAuth scope. This removes the admin's access to the workspace. In most cases their work is reassigned to the
## AI Content

 - [API Template](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/api_template.md): Schema: #/components/schemas/api_template
 - [API Template Source](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/api_template_source.md): Schema: #/components/schemas/api_template_source
 - [Content Import Source](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/content_import_source.md): Schema: #/components/schemas/content_import_source
 - [Content Import Sources](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/content_import_sources_list.md): Schema: #/components/schemas/content_import_sources_list
 - [External Page](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/external_page.md): Schema: #/components/schemas/external_page
 - [External Pages](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/external_pages_list.md): Schema: #/components/schemas/external_pages_list
 - [POST /ai/api_template_sources](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/createapitemplatesource.md): You can create a source that imports content from a knowledge base's REST API. Send a `template` that describes the vendor's API and an `auth_token` for the knowledge base. Write each value the vendor
 - [GET /ai/api_template_sources/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/getapitemplatesource.md): You can retrieve an API template source, including its template and the status of its latest sync. The `auth_token` is never returned. OAuth tokens must have the `read_write_ai_content` scope.
 - [POST /ai/api_template_sources/{id}/sync](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/syncapitemplatesource.md): You can start a sync of an API template source. Intercom fetches the knowledge base's pages again using the source's template and token, and updates the imported content. The response is the source, w
 - [GET /ai/content_import_sources](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/listcontentimportsources.md): You can retrieve a list of all content import sources for a workspace. `total_count` and `pages.total_pages` are worked out from every content import source in the workspace, including deleted ones th
 - [POST /ai/content_import_sources](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/createcontentimportsource.md): You can create a new content import source by sending a POST request to this endpoint. OAuth tokens must have the `read_write_ai_content` scope.
 - [DELETE /ai/content_import_sources/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/deletecontentimportsource.md): You can delete a content import source by making a DELETE request this endpoint. This will also delete all external pages that were imported from this source. OAuth tokens must have the `read_write_ai
 - [GET /ai/content_import_sources/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/getcontentimportsource.md): You can retrieve a content import source. OAuth tokens must have the `read_write_ai_content` scope.
 - [PUT /ai/content_import_sources/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/updatecontentimportsource.md): You can update an existing content import source. OAuth tokens must have the `read_write_ai_content` scope.
 - [GET /ai/external_pages](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/listexternalpages.md): You can retrieve a list of all external pages for a workspace. Send `source_id` and `external_id` together to get only the external page with that external ID. If no external page matches, the list is
 - [POST /ai/external_pages](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/createexternalpage.md): You can create a new external page by sending a POST request to this endpoint. If an external page already exists with the specified source_id and external_id, it will be updated instead. OAuth tokens
 - [DELETE /ai/external_pages/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/deleteexternalpage.md): Sending a DELETE request for an external page will remove it from the content library UI and from being used for AI answers. OAuth tokens must have the `read_write_ai_content` scope.
 - [GET /ai/external_pages/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/getexternalpage.md): You can retrieve an external page. OAuth tokens must have the `read_write_ai_content` scope.
 - [PUT /ai/external_pages/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/updateexternalpage.md): You can update an existing external page (if it was created via the API). OAuth tokens must have the `read_write_ai_content` scope.
 - [POST /ai/external_pages/{external_page_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/attachtagtoexternalpage.md): Apply an existing tag to an external page. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the
 - [DELETE /ai/external_pages/{external_page_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ai-content/detachtagfromexternalpage.md): Remove a tag from an external page. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Pag
## Articles

 - [Article](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article.md): Schema: #/components/schemas/article
 - [Internal Article](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/internal_article.md): Schema: #/components/schemas/internal_article
 - [Articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article_list_item.md): Schema: #/components/schemas/article_list_item
 - [Article Search Highlights](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article_search_highlights.md): Schema: #/components/schemas/article_search_highlights
 - [Article Search Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article_search_response.md): Schema: #/components/schemas/article_search_response
 - [Article Version](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article_version.md): Schema: #/components/schemas/article_version
 - [Article Version Summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/article_version_summary.md): Schema: #/components/schemas/article_version_summary
 - [GET /articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/listarticles.md): You can fetch a list of all articles by making a GET request to `https://api.intercom.io/articles`. > 📘 How are the articles sorted and ordered? Articles will be returned in descending order on the `
 - [POST /articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/createarticle.md): You can create a new article by making a POST request to `https://api.intercom.io/articles`. > 📘 Tags are managed separately Tags are returned in article responses but cannot be set in the request bo
 - [GET /articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/retrievearticle.md): You can fetch the details of a single article by making a GET request to `https://api.intercom.io/articles/<id>`. Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Inter
 - [PUT /articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/updatearticle.md): You can update the details of a single article by making a PUT request to `https://api.intercom.io/articles/<id>`. > 📘 Tags are managed separately Tags are returned in article responses but cannot be
 - [DELETE /articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/deletearticle.md): You can delete a single article by making a DELETE request to `https://api.intercom.io/articles/<id>`. Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`.
 - [GET /articles/{id}/draft](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/retrievearticledraft.md): Fetch the staged draft of a published article by making a GET request to `https://api.intercom.io/articles/<id>/draft`. The response is the article rendered with its draft content, leaving the live ar
 - [PUT /articles/{id}/draft](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/stagearticledraft.md): Stage changes to a published article as a draft by making a PUT request to `https://api.intercom.io/articles/<id>/draft`. The live article remains unchanged until the draft is published. The article m
 - [POST /articles/{id}/draft/publish](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/publisharticledraft.md): Publish a staged draft by making a POST request to `https://api.intercom.io/articles/<id>/draft/publish`, promoting the draft content to live. On a single-language workspace no body is required. On a
 - [GET /articles/{article_id}/versions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/listarticleversions.md): Fetch the version history of an article by making a GET request to `https://api.intercom.io/articles/<article_id>/versions`. Versions are returned newest-first as a paginated list of metadata. Use `GE
 - [GET /articles/{article_id}/versions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/retrievearticleversion.md): Fetch a single prior version of an article, including its body content, by making a GET request to `https://api.intercom.io/articles/<article_id>/versions/<id>`. Returns the version's full content; th
 - [POST /articles/{article_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/attachtagtoarticle.md): Apply an existing tag to an article. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the `manag
 - [DELETE /articles/{article_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/detachtagfromarticle.md): Remove a tag from an article. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Requires
 - [GET /articles/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/articles/searcharticles.md): You can search for articles by making a GET request to `https://api.intercom.io/articles/search`. If no articles match the search, `data` is an empty array rather than an object. Requires the `read_ar
## Away Status Reasons

 - [GET /away_status_reasons](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/away-status-reasons/listawaystatusreasons.md): Returns a list of all away status reasons configured for the workspace, including deleted ones.
## Audiences

 - [Audience](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/audience.md): Schema: #/components/schemas/audience
 - [GET /audiences](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/listaudiences.md): You can fetch a list of all audiences for the workspace. Requires the `read_audiences` or `read_write_audiences` OAuth scope.
 - [POST /audiences](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/createaudience.md): You can create a new audience by making a POST request to `https://api.intercom.io/audiences`. Requires the `read_write_audiences` OAuth scope.
 - [GET /audiences/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/retrieveaudience.md): You can fetch the details of a single audience by making a GET request to `https://api.intercom.io/audiences/{id}`. Requires the `read_audiences` or `read_write_audiences` OAuth scope.
 - [PUT /audiences/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/updateaudience.md): You can update the details of a single audience by making a PUT request to `https://api.intercom.io/audiences/{id}`. You can also send this request with `PATCH`; it behaves the same as `PUT`. Requires
 - [DELETE /audiences/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/audiences/deleteaudience.md): You can delete a single audience by making a DELETE request to `https://api.intercom.io/audiences/{id}`. An audience that is still used by other objects, such as a workflow, cannot be deleted. Require
## Auth Tokens

 - [Auth Token](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/auth_token.md): Schema: #/components/schemas/auth_token
 - [Create Auth Token Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/create_auth_token_request.md): Schema: #/components/schemas/create_auth_token_request
 - [OAuth Configuration](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/oauth_configuration.md): Schema: #/components/schemas/oauth_configuration
 - [Update Auth Token Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/update_auth_token_request.md): Schema: #/components/schemas/update_auth_token_request
 - [GET /auth_tokens](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/listauthtokens.md): Returns a paginated list of the workspace's stored third-party credentials. Use this to discover the id of a credential you want a data connector to authenticate with — that id is not otherwise availa
 - [POST /auth_tokens](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/createauthtoken.md): Stores a third-party credential in your workspace so a data connector can authenticate outbound requests with it. Set `token_type` to `text` (the default) to send the credential value as a request hea
 - [GET /auth_tokens/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/retrieveauthtoken.md): Returns the metadata for a single stored third-party credential. A credential that the list endpoint does not return is also not retrievable here, and responds with 404.
 - [PATCH /auth_tokens/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/auth-tokens/updateauthtoken.md): Updates the metadata of a stored third-party credential. A field you omit keeps its current value. The credential value itself cannot be changed here and is never returned. The `domain` is read-only,
## Banners

 - [Banner](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/banners/banner.md): Schema: #/components/schemas/banner
 - [Banner Dismiss](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/banners/banner_dismiss.md): Schema: #/components/schemas/banner_dismiss
 - [GET /contacts/{id}/banners](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/banners/listcontactbanners.md): Returns the banners a contact currently matches, so you can display them on surfaces outside the Messenger (native mobile apps, kiosks, embedded tools). Each banner in the response includes a `view_id
 - [POST /contacts/{id}/banners/{view_id}/dismiss](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/banners/dismisscontactbanner.md): Records that a contact has dismissed a banner. Dismissals are shared across surfaces, so a banner dismissed through this endpoint will also stop appearing in the web Messenger for that contact, and vi
## Brands

 - [Brand](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/brands/brand.md): Schema: #/components/schemas/brand
 - [Brand List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/brands/brand_list.md): Schema: #/components/schemas/brand_list
 - [GET /brands](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/brands/listbrands.md): Retrieves all brands for the workspace, including the default brand. The default brand id always matches the workspace id. Requires the `read_brands` OAuth scope.
 - [GET /brands/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/brands/retrievebrand.md): Fetches a specific brand by its unique identifier Requires the `read_brands` OAuth scope.
## Calls

 - [Call](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/call.md): Schema: #/components/schemas/call
 - [Call Transcript Turn](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/call_transcript_turn.md): Schema: #/components/schemas/call_transcript_turn
 - [GET /calls](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/listcalls.md): Retrieve a paginated list of calls. Requires the `read_conversations` OAuth scope.
 - [GET /calls/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/showcall.md): Retrieve a single call by id. Requires the `read_conversations` OAuth scope.
 - [GET /calls/{id}/recording](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/showcallrecording.md): Redirects to a signed URL for the call's recording if it exists. Requires the `read_conversations` OAuth scope.
 - [DELETE /calls/{id}/recording](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/deletecallrecording.md): Permanently deletes every recording of the call, including the part of the call handled by Fin, and the call's transcripts unless `include_transcripts` is `false`. Afterwards, the call's `recording_ur
 - [GET /calls/{id}/transcript](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/showcalltranscript.md): Returns the transcript for the specified call as a JSON array of turns. Each turn carries a `speaker_name` when the speaker could be resolved. Clients should fall back to `speaker_label` when `speaker
 - [POST /calls/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/listcallswithtranscripts.md): Retrieve calls by a list of conversation ids and include transcripts when available. A maximum of 20 `conversation_ids` can be provided. If none are provided or more than 20 are provided, a 400 error
 - [POST /fin_voice/register](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/registerfinvoicecall.md): Register a Fin Voice call with Intercom. This endpoint creates an external reference that links an external call identifier to an Intercom call and conversation. The call can be from different sources
 - [GET /fin_voice/collect/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/collectfinvoicecallbyid.md): Retrieve information about a Fin Voice call using the external reference ID. Requires the `read_conversations` OAuth scope.
 - [GET /fin_voice/external_id/{external_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/collectfinvoicecallbyexternalid.md): Retrieve information about a Fin Voice call using the external call identifier. Requires the `read_conversations` OAuth scope.
 - [GET /fin_voice/phone_number/{phone_number}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/collectfinvoicecallbyphonenumber.md): Retrieve information about a Fin Voice call using the phone number. Returns the most recent matched call for the given phone number, ordered by creation date. Requires the `read_conversations` OAuth s
 - [GET /fin_voice/conversation/{conversation_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/calls/collectfinvoicecallsbyconversationid.md): Retrieve information about Fin Voice calls associated with a conversation. Returns all matched calls for the given conversation ID. A conversation may have multiple associated calls. Requires the `rea
## Companies

 - [Company](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/company.md): Schema: #/components/schemas/company
 - [Companies Bulk Job](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/companies_bulk_job.md): Schema: #/components/schemas/companies_bulk_job
 - [POST /companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/createorupdatecompany.md): You can create or update a company. Companies will be only visible in Intercom when there is at least one associated user. Companies are looked up via `company_id` in a `POST` request, if not found vi
 - [GET /companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/retrievecompany.md): You can fetch a single company by passing in `company_id` or `name`. `https://api.intercom.io/companies?name={name}` `https://api.intercom.io/companies?company_id={company_id}` You can fetch all compa
 - [GET /companies/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/retrieveacompanybyid.md): You can fetch a single company.
 - [PUT /companies/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/updatecompany.md): You can update a single company using the Intercom provisioned `id`. Every custom attribute you send must already exist in your workspace. Sending one that doesn't returns a `400` error. You can also
 - [DELETE /companies/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/deletecompany.md): Delete a single company. Deleting a company is permanent and can't be reversed. The company record is removed from your workspace, along with its notes, tags and external references. Its contacts are
 - [GET /companies/{id}/contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listattachedcontacts.md): You can fetch a list of all contacts that belong to a company. Requires the `read_users_companies` OAuth scope.
 - [GET /companies/{id}/segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listattachedsegmentsforcompanies.md): You can fetch a list of all segments that belong to a company. Requires the `read_users_companies` OAuth scope.
 - [GET /companies/{company_id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listcompanynotes.md): You can fetch a list of notes that are associated to a company. Requires the `read_users_companies` OAuth scope.
 - [POST /companies/{company_id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/createcompanynote.md): You can add a note to a single company. Requires the `write_users_companies` OAuth scope.
 - [POST /companies/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/searchcompanies.md): You can search for companies by the value of their attributes in order to fetch exactly the companies you want. To search for companies, send a `POST` request to `https://api.intercom.io/companies/sea
 - [POST /companies/list](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listallcompanies.md): You can list companies. The company list is sorted by the `last_request_at` field and by default is ordered descending, most recently requested first. Note that the API does not include companies who
 - [GET /companies/scroll](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/scrolloverallcompanies.md): The `list all companies` functionality does not work well for huge datasets, and can result in errors and performance problems when paging deeply. The Scroll API provides an efficient mechanism for it
 - [POST /contacts/{id}/companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/attachcontacttoacompany.md): You can attach a company to a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/{id}/companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listcompaniesforacontact.md): You can fetch a list of companies that are associated to a contact.
 - [DELETE /contacts/{contact_id}/companies/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/detachcontactfromacompany.md): You can detach a company from a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [POST /companies/bulk](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/bulkcreatecompanies.md): You can bulk create or update companies by submitting an array of company objects. Each company is matched on the `company_id` you have defined for it: a new company is created if none exists with tha
 - [PUT /companies/bulk](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/bulkupdatecompanies.md): You can bulk update companies by submitting an array of company objects with the fields to update. Each company must include an `id` field identifying the company to update by its Intercom company `id
 - [POST /companies/bulk/delete](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/bulkdeletecompanies.md): You can bulk delete companies by submitting an array of companies, each identified by its Intercom company `id`. Each company is permanently deleted, the same as with the single [Delete a company](/do
 - [GET /companies/bulk/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/showbulkcompaniesjob.md): You can check the status of a bulk companies job. The `state` field indicates the overall job progress: `pending`, `running`, `completed`, or `completed_with_errors`.
 - [GET /contacts/{contact_id}/granted_companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/listgrantedcompaniesforacontact.md): List the companies a contact has been granted access to. A granted company lets the contact read that company's tickets in the customer portal. It is separate from company membership — granting a comp
 - [PUT /contacts/{contact_id}/granted_companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/replacegrantedcompaniesforacontact.md): Replace the full set of companies a contact has been granted access to. This is a replacement, not an append. The `company_ids` you send become the contact's entire granted set — any company id you le
 - [DELETE /contacts/{contact_id}/granted_companies/{company_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/companies/removegrantedcompanyfromacontact.md): Remove a single company from a contact's granted set, leaving the contact's other grants in place. Identify the company by the `company_id` you set on it, the same value [`GET /contacts/{contact_id}/g
## Contacts

 - [Contact](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/contact.md): Schema: #/components/schemas/contact
 - [Contacts Bulk Job](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/contacts_bulk_job.md): Schema: #/components/schemas/contacts_bulk_job
 - [GET /companies/{id}/contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listattachedcontacts.md): You can fetch a list of all contacts that belong to a company. Requires the `read_users_companies` OAuth scope.
 - [POST /contacts/{id}/companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/attachcontacttoacompany.md): You can attach a company to a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/{id}/companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listcompaniesforacontact.md): You can fetch a list of companies that are associated to a contact.
 - [DELETE /contacts/{contact_id}/companies/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/detachcontactfromacompany.md): You can detach a company from a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/{contact_id}/granted_companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listgrantedcompaniesforacontact.md): List the companies a contact has been granted access to. A granted company lets the contact read that company's tickets in the customer portal. It is separate from company membership — granting a comp
 - [PUT /contacts/{contact_id}/granted_companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/replacegrantedcompaniesforacontact.md): Replace the full set of companies a contact has been granted access to. This is a replacement, not an append. The `company_ids` you send become the contact's entire granted set — any company id you le
 - [DELETE /contacts/{contact_id}/granted_companies/{company_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/removegrantedcompanyfromacontact.md): Remove a single company from a contact's granted set, leaving the contact's other grants in place. Identify the company by the `company_id` you set on it, the same value [`GET /contacts/{contact_id}/g
 - [GET /contacts/{id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listnotes.md): You can fetch a list of notes that are associated to a contact. Requires the `read_users_companies` or `read_write_users` OAuth scope.
 - [POST /contacts/{id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/createnote.md): You can add a note to a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/{contact_id}/segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listsegmentsforacontact.md): You can fetch a list of segments that are associated to a contact. Requires the `read_users_companies` or `read_write_users` OAuth scope.
 - [GET /contacts/{contact_id}/subscriptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listsubscriptionsforacontact.md): You can fetch a list of subscription types that are attached to a contact. These can be subscriptions that a user has 'opted-in' to or has 'opted-out' from, depending on the subscription type. This wi
 - [POST /contacts/{contact_id}/subscriptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/attachsubscriptiontypetocontact.md): You can add a specific subscription to a contact. In Intercom, we have two different subscription types based on user consent - opt-out and opt-in: 1.Attaching a contact to an opt-out subscription typ
 - [DELETE /contacts/{contact_id}/subscriptions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/detachsubscriptiontypetocontact.md): You can remove a specific subscription from a contact. This will return a subscription type model for the subscription type that was removed from the contact. Requires the `read_write_users` or `write
 - [GET /contacts/{contact_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listtagsforacontact.md): You can fetch a list of all tags that are attached to a specific contact.
 - [POST /contacts/{contact_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/attachtagtocontact.md): You can tag a specific contact. This will return a tag object for the tag that was added to the contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [DELETE /contacts/{contact_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/detachtagfromcontact.md): You can remove tag from a specific contact. This will return a tag object for the tag that was removed from the contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listdeletedcontacts.md): Fetch a paginated list of the contacts in your workspace that are no longer active, so you can recover ones whose `id`, `email`, or `external_id` you no longer have and then permanently delete them. E
 - [PUT /contacts/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/updatecontact.md): You can update an existing contact (ie. user or lead). This endpoint handles both **contact updates** and **custom object associations**. See *`update a contact with an association to a custom object
 - [GET /contacts/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/showcontact.md): You can fetch the details of a single contact. If a contact has been merged into another contact via the Merge endpoint (`POST /contacts/merge`), requesting it by its original ID will return **HTTP 41
 - [DELETE /contacts/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/deletecontact.md): You can delete a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [POST /contacts/merge](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/mergecontact.md): You can merge one contact into another. Both lead-into-user and user-into-user merges are supported: the source contact (`from`) may have a `role` of `lead` or `user`, and the destination contact (`in
 - [POST /contacts/merge/preview](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/previewmergecontact.md): Preview the result of merging one contact into another without applying the merge. This is a read-only dry run: it reports whether the merge is allowed and, if so, exactly what would change, **without
 - [POST /contacts/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/searchcontacts.md): You can search for multiple contacts by the value of their attributes in order to fetch exactly who you want. To search for contacts, you need to send a `POST` request to `https://api.intercom.io/cont
 - [GET /contacts/activities](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listcontactactivities.md): You can fetch a list of contact activity events for your workspace, such as when contacts are created, role updated, merged, or deleted. Events are returned oldest first. If the activity store can't b
 - [GET /contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listcontacts.md): You can fetch a list of all contacts (ie. users or leads) in your workspace. Contacts that have been merged (via POST /contacts/merge) will not appear in list results. Only the target contact from the
 - [POST /contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/createcontact.md): You can create a new contact (ie. user or lead). Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /contacts/find_by_external_id/{external_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/showcontactbyexternalid.md): You can fetch the details of a single contact by external ID. Note that this endpoint only supports users and not leads. If the contact with this external ID has been merged into another contact, the
 - [POST /contacts/{id}/archive](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/archivecontact.md): You can archive a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [POST /contacts/{id}/unarchive](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/unarchivecontact.md): You can unarchive a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [POST /contacts/{id}/block](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/blockcontact.md): Block a single contact.**Note:** conversations of the contact will also be archived during the process.More details in [FAQ How do I block Inbox spam?](https://www.intercom.com/help/en/articles/883865
 - [GET /contacts/{id}/merge_histories](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listcontactmergehistory.md): Retrieve the paginated list of contacts that have been merged into a given contact. Only available for contacts with a `user` role. Returns a `404` if the contact is not found or has a `lead` role. Re
 - [GET /contacts/{id}/banners](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/listcontactbanners.md): Returns the banners a contact currently matches, so you can display them on surfaces outside the Messenger (native mobile apps, kiosks, embedded tools). Each banner in the response includes a `view_id
 - [POST /contacts/{id}/banners/{view_id}/dismiss](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/dismisscontactbanner.md): Records that a contact has dismissed a banner. Dismissals are shared across surfaces, so a banner dismissed through this endpoint will also stop appearing in the web Messenger for that contact, and vi
 - [POST /contacts/bulk](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/bulkcreatecontacts.md): You can bulk create contacts by submitting an array of contact objects. This is a **strict create** and never updates an existing contact. The endpoint creates an async job that processes the items in
 - [PUT /contacts/bulk](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/bulkupdatecontacts.md): You can bulk update contacts by submitting an array of contact objects with the fields to update. Each contact must include an `id` field identifying the contact to update. You can also add or remove
 - [POST /contacts/bulk/delete](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/bulkdeletecontacts.md): You can delete contacts in bulk by submitting an array of contact `id`s. The endpoint creates an async job that processes the deletes in the background. Use the returned job ID with `GET /contacts/bul
 - [GET /contacts/bulk/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/contacts/showbulkupdatecontactsjob.md): You can check the status of a bulk contact update job. The `state` field indicates the overall job progress: `running`, `completed`, or `completed_with_errors`. Requires the `read_users_companies` or
## Content

 - [POST /content/bulk_actions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content/bulkcontentactions.md): Asynchronously run a bulk action over up to 1,000 Knowledge Hub content items. Six actions are supported: * `publish` and `unpublish` — apply to `article_content` only. * `delete` — permanently de
 - [GET /content/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content/searchcontent.md): Search across Knowledge Hub content of all supported types in a single call: articles, content snippets, external content (webpages), file source content (uploaded documents), and internal articles. A
## Content Snippets

 - [Content Snippet](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/content_snippet.md): Schema: #/components/schemas/content_snippet
 - [GET /content_snippets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/listcontentsnippets.md): You can fetch a list of all content snippets for a workspace. Requires the `read_content_snippets` or `read_write_content_snippets` OAuth scope.
 - [POST /content_snippets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/createcontentsnippet.md): You can create a new content snippet. `title` is listed as required, but a missing, `null` or empty `title` is accepted and the snippet is created with a blank title. When `json_blocks` is omitted or
 - [GET /content_snippets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/getcontentsnippet.md): You can fetch a single content snippet by its id. Requires the `read_content_snippets` or `read_write_content_snippets` OAuth scope.
 - [PUT /content_snippets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/updatecontentsnippet.md): You can update an existing content snippet. Requires the `read_write_content_snippets` OAuth scope.
 - [DELETE /content_snippets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/deletecontentsnippet.md): You can delete a single content snippet by its id. Requires the `read_write_content_snippets` OAuth scope.
 - [POST /content_snippets/{content_snippet_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/attachtagtocontentsnippet.md): Apply an existing tag to a content snippet. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the
 - [DELETE /content_snippets/{content_snippet_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/content-snippets/detachtagfromcontentsnippet.md): Remove a tag from a content snippet. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Re
## Conversations

 - [Conversation List Item](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_list_item.md): Schema: #/components/schemas/conversation_list_item
 - [Conversation](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation.md): Schema: #/components/schemas/conversation
 - [Conversation Monitor Evaluation](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_monitor_evaluation.md): Schema: #/components/schemas/conversation_monitor_evaluation
 - [Conversation Scorecard](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard.md): Schema: #/components/schemas/conversation_scorecard
 - [Reviewer](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_reviewer.md): Schema: #/components/schemas/conversation_scorecard_reviewer
 - [Submitted By](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_submitted_by.md): Schema: #/components/schemas/conversation_scorecard_submitted_by
 - [Revised By](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_revised_by.md): Schema: #/components/schemas/conversation_scorecard_revised_by
 - [Scorecard Note](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_note.md): Schema: #/components/schemas/conversation_scorecard_note
 - [Note Author](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_note_author.md): Schema: #/components/schemas/conversation_scorecard_note_author
 - [Reviewed Teammate](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_reviewed_teammate.md): Schema: #/components/schemas/conversation_scorecard_reviewed_teammate
 - [Conversation Scorecard Evaluator](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_evaluator.md): Schema: #/components/schemas/conversation_scorecard_evaluator
 - [Conversation Scorecard Evaluator Result](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_evaluator_result.md): Schema: #/components/schemas/conversation_scorecard_evaluator_result
 - [Evaluator Reason](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_scorecard_evaluator_reason.md): Schema: #/components/schemas/conversation_scorecard_evaluator_reason
 - [Conversation stream token](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/conversation_stream_token.md): Schema: #/components/schemas/conversation_stream_token
 - [Rated conversation](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/rated_conversation.md): Schema: #/components/schemas/rated_conversation
 - [Merge Conversations Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/merge_conversations_request.md): Schema: #/components/schemas/merge_conversations_request
 - [POST /conversations/{conversation_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/attachtagtoconversation.md): You can tag a specific conversation. This will return a tag object for the tag that was added to the conversation. If the conversation is a ticket, the access token must include the `write_tickets` sc
 - [DELETE /conversations/{conversation_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/detachtagfromconversation.md): You can remove tag from a specific conversation. This will return a tag object for the tag that was removed from the conversation. If the conversation is a ticket, the access token must include the `w
 - [GET /conversations](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listconversations.md): You can fetch a list of all conversations. You can optionally request the result page size and the cursor to start after to fetch the result. You can use pagination to limit the number of results retu
 - [POST /conversations](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/createconversation.md): You can create a conversation that has been initiated by a contact (ie. user or lead). The conversation can be an in-app message only. You can also send a message from a visitor by specifying their `i
 - [GET /conversations/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/retrieveconversation.md): You can fetch the details of a single conversation. This will return a single Conversation model with all its conversation parts. Without `page`, the response returns the 500 most recent conversation
 - [PUT /conversations/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/updateconversation.md): You can update an existing conversation. If you want to reply to a coveration or take an action such as assign, unassign, open, close or snooze, take a look at the reply and manage endpoints. This end
 - [DELETE /conversations/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/deleteconversation.md): With `retain_metrics=false`, deleting a conversation is permanent and cannot be reversed. With the default `retain_metrics=true`, the conversation's data is retained for 7 days before being permanentl
 - [POST /conversations/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/searchconversations.md): You can search for multiple conversations by the value of their attributes in order to fetch exactly which ones you want. To search for conversations, you need to send a `POST` request to `https://api
 - [POST /conversations/{id}/reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/replyconversation.md): You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins. By default, bot or Operator replies to an inbound email conversation aren't sent to y
 - [POST /conversations/{id}/parts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/manageconversation.md): For managing conversations you can: - Close a conversation - Snooze a conversation to reopen on a future date - Open a conversation which is `snoozed` or `closed` - Assign a conversation to an admin
 - [GET /conversations/{id}/handling_events](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listhandlingevents.md): List all pause/resume events for a conversation. These events track when teammates paused or resumed handling a conversation. Requires the `read_conversations` OAuth scope.
 - [GET /conversations/{id}/team_handling_segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listteamhandlingsegments.md): Shows the time teammates spent actively working on a conversation, and which team the conversation was assigned to while they did. Each period covers a single team assignment, and never continues acro
 - [GET /conversations/{id}/hitl_events](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listhitlevents.md): List the human-in-the-loop (HITL) events for a conversation. When Fin is unsure of an answer it can consult a teammate before replying, proposing a draft that the teammate approves, steers with free-t
 - [GET /conversations/{id}/side_conversations](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listsideconversations.md): List side conversations for a given conversation. Side conversations are internal threads created by teammates from within a conversation. Each side conversation includes its conversation parts (messa
 - [POST /conversations/{conversation_id}/rating](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/rateconversation.md): Record a contact's CSAT rating, and an optional remark, on the latest rating request Intercom sent for a conversation. The rating counts in your CSAT reports for the teammate, Fin or workflow that was
 - [POST /conversations/{id}/merge](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/mergeconversation.md): Merge a secondary (source) conversation into a primary (target) conversation. The secondary conversation is closed and linked to the primary, which becomes the surviving thread. Returns the primary co
 - [POST /conversations/{id}/convert](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/convertconversationtoticket.md): You can convert a conversation to a ticket.
 - [GET /conversations/deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/listdeletedconversationids.md): List all deleted conversation IDs. You can use pagination to limit the number of results returned. The default is `20` results per page. You can navigate to next pages using the `page` param.
 - [POST /conversations/stream/token](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/createconversationstreamtoken.md): Realtime streaming of conversation events uses Server-Sent Events (SSE). It is an opt-in feature, enabled per workspace. Contact Intercom to turn it on. Issue a token that a contact's client uses to s
 - [DELETE /conversations/stream/token](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations/revokeconversationstreamtokens.md): Realtime streaming of conversation events uses Server-Sent Events (SSE). It is an opt-in feature, enabled per workspace. Contact Intercom to turn it on. Revoke every active conversation stream token f
## Conversation Parts

 - [PUT /conversations/{conversation_id}/conversation_parts/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversation-parts/updateconversationpart.md): You can update properties of a conversation part. Currently supports updating the send state of an external reply or marking a part as seen by an admin. This is an experimental endpoint. It requires a
 - [POST /conversations/redact](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversation-parts/redactconversation.md): You can redact a conversation part or the source message of a conversation (as seen in the source object). If you are redacting a conversation part, it must have a `body`. If you are redacting a sourc
## Conversation Participants

 - [POST /conversations/{id}/customers](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversation-participants/attachcontacttoconversation.md): You can add participants who are contacts to a conversation, on behalf of either another contact or an admin. If you add a contact via the email parameter and there is no user/lead found on that works
 - [DELETE /conversations/{conversation_id}/customers/{contact_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversation-participants/detachcontactfromconversation.md): You can remove participants who are contacts from a group conversation, on behalf of an admin. You cannot remove the last remaining contact from a conversation. If the conversation is a ticket, the ac
## Conversations Attributes

 - [Conversation Attribute](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/conversation_attribute.md): Schema: #/components/schemas/conversation_attribute
 - [GET /conversations/attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/listconversationattributes.md): You can fetch a list of all conversation attributes for your workspace.
 - [POST /conversations/attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/createconversationattribute.md): Create a new conversation attribute.
 - [GET /conversations/attributes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/getconversationattribute.md): Retrieve a single conversation attribute by ID.
 - [PUT /conversations/attributes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/updateconversationattribute.md): Update an existing conversation attribute.
 - [DELETE /conversations/attributes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/deleteconversationattribute.md): Archive a conversation attribute (soft delete). The attribute is marked as archived but not permanently deleted.
 - [POST /conversations/attributes/{id}/options](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/createconversationattributeoption.md): Add a new option to a list-type conversation attribute. Returns the full attribute with the updated options array.
 - [PUT /conversations/attributes/{id}/options/{option_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/updateconversationattributeoption.md): Update the label of a single option on a list-type conversation attribute. Returns the full attribute with the updated options array.
 - [DELETE /conversations/attributes/{id}/options/{option_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/conversations-attributes/deleteconversationattributeoption.md): Archive a single option on a list-type conversation attribute (soft delete). The option remains in the response with `archived: true`. Returns the full attribute with the updated options array.
## Custom Object Instances

 - [Custom Object Instance](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/custom_object_instance.md): Schema: #/components/schemas/custom_object_instance
 - [Custom Object Instances](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/custom_object_instances_paginated_list.md): Schema: #/components/schemas/custom_object_instances_paginated_list
 - [PUT /contacts/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/updatecontact.md): You can update an existing contact (ie. user or lead). This endpoint handles both **contact updates** and **custom object associations**. See *`update a contact with an association to a custom object
 - [PUT /conversations/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/updateconversation.md): You can update an existing conversation. If you want to reply to a coveration or take an action such as assign, unassign, open, close or snooze, take a look at the reply and manage endpoints. This end
 - [POST /custom_object_instances/{custom_object_type_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/createcustomobjectinstances.md): Create or update a custom object instance Requires the `read_write_custom_object_instances` OAuth scope.
 - [GET /custom_object_instances/{custom_object_type_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/listcustomobjectinstances.md): List instances of a custom object type. Three modes are supported: - **No filter** — returns all instances for the type. - **`references_contact_id`** — returns instances associated with the given c
 - [DELETE /custom_object_instances/{custom_object_type_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/deletecustomobjectinstancesbyexternalid.md): Delete a single Custom Object instance by external_id. Requires the `read_write_custom_object_instances` OAuth scope.
 - [GET /custom_object_instances/{custom_object_type_identifier}/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/getcustomobjectinstancesbyid.md): Fetch a Custom Object Instance by id. Requires the `read_conversations`, `read_users_companies`, `read_write_custom_object_instances` or `read_write_users` OAuth scope.
 - [DELETE /custom_object_instances/{custom_object_type_identifier}/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/custom-object-instances/deletecustomobjectinstancesbyid.md): Delete a single Custom Object instance using the Intercom defined id. Requires the `read_write_custom_object_instances` OAuth scope.
## Data Attributes

 - [Data Attribute](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-attributes/data_attribute.md): Schema: #/components/schemas/data_attribute
 - [GET /data_attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-attributes/lisdataattributes.md): You can fetch a list of all data attributes belonging to a workspace for contacts or companies. Conversation attributes are no longer returned by this endpoint. Calling without a `model` parameter no
 - [POST /data_attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-attributes/createdataattribute.md): You can create a data attributes for a `contact` or a `company`. Requires the `write_attributes` OAuth scope.
 - [PUT /data_attributes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-attributes/updatedataattribute.md): You can update a data attribute. > 🚧 Updating the data type is not possible It is currently a dangerous action to execute changing a data attribute's type via the API. You will need to update the typ
## Data Connectors

 - [Data Connector](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector.md): Schema: #/components/schemas/data_connector
 - [Data Connector (Detail)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_detail.md): Schema: #/components/schemas/data_connector_detail
 - [Data Connector Execution Result](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_execution_result.md): Schema: #/components/schemas/data_connector_execution_result
 - [Data Connector Health](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health.md): Schema: #/components/schemas/data_connector_health
 - [Data Connector Health Summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health_summary.md): Schema: #/components/schemas/data_connector_health_summary
 - [Data Connector Health Percentiles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health_percentiles.md): Schema: #/components/schemas/data_connector_health_percentiles
 - [Data Connector Health Status Count](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health_status_count.md): Schema: #/components/schemas/data_connector_health_status_count
 - [Data Connector Health Failure Count](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health_failure_count.md): Schema: #/components/schemas/data_connector_health_failure_count
 - [Data Connector Health Time Series Point](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_health_time_series_point.md): Schema: #/components/schemas/data_connector_health_time_series_point
 - [Data Connector Version](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/data_connector_version.md): Schema: #/components/schemas/data_connector_version
 - [GET /data_connectors](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/listdataconnectors.md): Returns a paginated list of all data connectors for the workspace, ordered by most recently updated first. Data connectors allow workflows and AI agents to make HTTP requests to external APIs. OAuth t
 - [POST /data_connectors](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/createdataconnector.md): Create a new data connector. The connector is created in `draft` state. Configure its URL, headers, data inputs, and other settings, then set it to `live` when ready. OAuth tokens must have the `read_
 - [GET /data_connectors/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/retrievedataconnector.md): You can retrieve the full detail of a single data connector by its ID. The response includes configuration, data inputs, response fields, and object mappings. OAuth tokens must have the `read_workflow
 - [DELETE /data_connectors/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/deletedataconnector.md): Delete an existing data connector. The connector must be in `draft` state and must not be in use by any workflows or AI agents. OAuth tokens must have the `read_write_data_connectors` scope.
 - [PATCH /data_connectors/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/updatedataconnector.md): Update an existing data connector. Only provided fields are changed. Set `state` to `live` or `draft` to change the connector's state. OAuth tokens must have the `read_write_data_connectors` scope.
 - [GET /data_connectors/{data_connector_id}/execution_results](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/listdataconnectorexecutionresults.md): Retrieve paginated execution logs for a specific data connector. Results from the last hour are returned by default. Use `start_ts` and `end_ts` to customize the time range. Request/response bodies ar
 - [GET /data_connectors/{data_connector_id}/execution_results/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/showdataconnectorexecutionresult.md): Retrieve details for a specific data connector execution result. Includes the sanitised request URL, and the request/response bodies when they are available. Bodies are omitted when the request comes
 - [GET /data_connectors/{data_connector_id}/health](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/getdataconnectorhealth.md): Retrieve aggregated execution health for a data connector: success rate, latency and payload size percentiles, a breakdown of HTTP statuses and failure reasons, and a time series over the requested ra
 - [GET /data_connectors/{id}/versions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/listdataconnectorversions.md): Retrieve the version history of a data connector, newest first. Each entry is a point-in-time snapshot of the connector's configuration, with the status it has today and an optional note. Results are
 - [GET /data_connectors/{id}/versions/{version_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/retrievedataconnectorversion.md): Retrieve a single version of a data connector, including the connector configuration as it was at that version. Requires the `read_data_connector_versions` or `read_write_data_connector_versions` OAut
 - [PATCH /data_connectors/{id}/versions/{version_id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-connectors/updatedataconnectorversion.md): Update the note on a data connector version. The note is the only field that can be changed. This does not publish the version or roll the connector back to it. Send an empty string to clear the note.
## Data Events

 - [Data Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-events/data_event.md): Schema: #/components/schemas/data_event
 - [POST /events](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-events/createdataevent.md): You will need an Access Token that has write permissions to send Events. Once you have a key you can submit events via POST to the Events resource, which is located at https://api.intercom.io/events,
 - [GET /events](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-events/lisdataevents.md): > 🚧 Please note that you can only 'list' events that are less than 90 days old. Event counts and summaries will still include your events older than 90 days but you cannot 'list' these events individ
 - [POST /events/summaries](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-events/dataeventsummaries.md): Create event summaries for a user. Event summaries are used to track the number of times an event has occurred, the first time it occurred and the last time it occurred. Identify the user with one of
## Data Export

 - [Data Export](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-export/data_export.md): Schema: #/components/schemas/data_export
 - [POST /export/content/data](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-export/createdataexport.md): To create your export job, you need to send a `POST` request to the export endpoint `https://api.intercom.io/export/content/data`. This endpoint exports **message delivery and engagement data** for ou
 - [GET /export/content/data/{job_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-export/getdataexport.md): You can view the status of your job by sending a `GET` request to the URL `https://api.intercom.io/export/content/data/{job_identifier}` - the `{job_identifier}` is the value returned in the response
 - [POST /export/cancel/{job_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-export/canceldataexport.md): You can cancel your job. A job that has already reached a terminal state is returned unchanged. Requires the `export_content_data` OAuth scope.
 - [GET /download/content/data/{job_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/data-export/downloaddataexport.md): When a job has a status of complete, and thus a filled download_url, you can download your data by hitting that provided URL, formatted like so: https://api.intercom.io/download/content/data/xyz1234.
## Ecommerce Connectors

 - [POST /ecommerce/connectors/{id}/catalog](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ecommerce-connectors/uploadecommercecatalog.md): Upload a product catalog to an ecommerce connector. The catalog must be a JSON array of product objects. There are two upload modes: **Single-file upload** — POST a single catalog file (up to 99 MB pe
 - [POST /ecommerce/connectors/{id}/events](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ecommerce-connectors/submitecommerceproductevent.md): Send a single product or order change to an ecommerce connector. Use product events to keep Fin's product knowledge current between full catalog uploads, and order events to tell Fin about the orders
## Dynamic Content

 - [Dynamic Content](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/dynamic_content.md): Schema: #/components/schemas/dynamic_content
 - [Dynamic Content Variation](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/dynamic_content_variation.md): Schema: #/components/schemas/dynamic_content_variation
 - [GET /dynamic_contents](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/listdynamiccontents.md): You can fetch a list of all dynamic content for a workspace, most recently updated first. Requires the `read_dynamic_content` or `read_write_dynamic_content` OAuth scope.
 - [POST /dynamic_contents](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/createdynamiccontent.md): You can create dynamic content. Requires the `read_write_dynamic_content` OAuth scope.
 - [GET /dynamic_contents/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/getdynamiccontent.md): You can fetch a single dynamic content by its id. Requires the `read_dynamic_content` or `read_write_dynamic_content` OAuth scope.
 - [PUT /dynamic_contents/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/updatedynamiccontent.md): You can update existing dynamic content. Only the fields you provide are changed. You can also send this request with `PATCH`; it behaves the same as `PUT`. Requires the `read_write_dynamic_content` O
 - [DELETE /dynamic_contents/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/dynamic-content/deletedynamiccontent.md): You can delete a single dynamic content by its id. Dynamic content that is still used in an article can't be deleted. Requires the `read_write_dynamic_content` OAuth scope.
## Emails

 - [Email Setting](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/emails/email_setting.md): Schema: #/components/schemas/email_setting
 - [Email List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/emails/email_list.md): Schema: #/components/schemas/email_list
 - [GET /emails](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/emails/listemails.md): Lists all sender email address settings for the workspace Requires the `read_emails` OAuth scope.
 - [GET /emails/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/emails/retrieveemail.md): Fetches a specific email setting by its unique identifier Requires the `read_emails` OAuth scope.
## Fin Agent

 - [Fin Agent Message](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_message.md): Schema: #/components/schemas/fin_agent_message
 - [Fin Agent User](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_user.md): Schema: #/components/schemas/fin_agent_user
 - [Fin Agent Attachment](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_attachment.md): Schema: #/components/schemas/fin_agent_attachment
 - [Fin Agent Conversation Metadata](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_conversation_metadata.md): Schema: #/components/schemas/fin_agent_conversation_metadata
 - [Fin Agent Attribute Errors](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_attribute_errors.md): Schema: #/components/schemas/fin_agent_attribute_errors
 - [Fin Agent Status Updated Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_status_updated_event.md): Schema: #/components/schemas/fin_agent_status_updated_event
 - [Fin Agent Replied Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_replied_event.md): Schema: #/components/schemas/fin_agent_replied_event
 - [Fin Agent CSAT Requested Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/fin_agent_csat_requested_event.md): Schema: #/components/schemas/fin_agent_csat_requested_event
 - [POST /fin/capabilities](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/listfincapabilities.md): Return a machine-readable, per-user list of what Fin can do for a given end user, so an orchestrating agent can decide which endpoint to call. The response is audience-matched to the supplied user: ea
 - [POST /fin/ask](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/askfin.md): Ask Fin a single, self-contained question and receive one informational answer. Unlike a conversation, `/fin/ask` is non-conversational: Fin will not ask follow-up questions, will not run procedures,
 - [POST /fin/reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/replytofin.md): Send a follow-up message in an existing conversation. When Fin needs more information to complete an action, it sets the conversation to `awaiting_user_reply` — send the user's response so Fin can con
 - [POST /fin/procedures/{procedure_id}/run](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/runfinprocedure.md): Deterministically run a specific procedure on a new conversation. Calling this endpoint guarantees that the named procedure runs — there is no non-deterministic routing. Fin's progress is delivered as
 - [POST /fin/escalate](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/escalatefinconversation.md): Hand a conversation off to a human teammate. If you use the Intercom Helpdesk, the handoff lands in your team inbox. Provide either `conversation_id` or `user`: - `conversation_id` — escalate an exis
 - [POST /fin/csat](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/submitfincsat.md): Record a customer's satisfaction rating for a conversation, with an optional free-text remark. Fin decides *when* to ask for a rating — this reuses the CSAT settings on your Fin workflow, not this API
 - [POST /fin/start](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-agent/startfinconversation.md): Initialize Fin by passing it the user's message along with conversation history and user details. These additional pieces of context will be used by Fin to provide a better and more contextual answer
## Fin Tasks

 - [Fin Task](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/fin_task.md): Schema: #/components/schemas/fin_task
 - [GET /fin/tasks](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/listfintasks.md): You can fetch a list of all Fin Tasks (AI agent workflows) configured for your workspace.
 - [POST /fin/tasks](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/createfintask.md): You can create a new Fin Task (AI agent workflow). Set `activate` to `true` to make the task live immediately, otherwise it is created as a draft. If activation fails, the task is still created as a d
 - [GET /fin/tasks/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/retrievefintask.md): You can fetch the details of a single Fin Task by its id.
 - [PUT /fin/tasks/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/updatefintask.md): You can update the title and description of an existing Fin Task, and set the audience segments it is available to. `title` and `description` must always be sent together, including when you only want
 - [DELETE /fin/tasks/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/fin-tasks/deletefintask.md): You can delete a Fin Task by passing in its id. This deactivates the task, if live, before deleting it.
## Help Center

 - [Collection](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/collection.md): Schema: #/components/schemas/collection
 - [Help Center Redirect](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/help_center_redirect.md): Schema: #/components/schemas/help_center_redirect
 - [Help Center](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/help_center.md): Schema: #/components/schemas/help_center
 - [Help Centers](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/help_center_list.md): Schema: #/components/schemas/help_center_list
 - [GET /help_center/help_centers/{help_center_id}/redirects](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/listhelpcenterredirects.md): You can fetch a list of all URL redirects for a help center by making a GET request to `https://api.intercom.io/help_center/help_centers/{help_center_id}/redirects`. Redirects are returned in ascendin
 - [POST /help_center/help_centers/{help_center_id}/redirects](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/createhelpcenterredirect.md): You can create a new URL redirect by making a POST request to `https://api.intercom.io/help_center/help_centers/{help_center_id}/redirects`. Requires the `read_write_help_center_redirects_scope` OAuth
 - [GET /help_center/help_centers/{help_center_id}/redirects/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/retrievehelpcenterredirect.md): You can fetch the details of a single redirect by making a GET request to `https://api.intercom.io/help_center/help_centers/{help_center_id}/redirects/{id}`. Requires the `read_help_center_redirects_s
 - [DELETE /help_center/help_centers/{help_center_id}/redirects/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/deletehelpcenterredirect.md): You can delete a single redirect by making a DELETE request to `https://api.intercom.io/help_center/help_centers/{help_center_id}/redirects/{id}`. Requires the `read_write_help_center_redirects_scope`
 - [GET /help_center/collections](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/listallcollections.md): You can fetch a list of all collections by making a GET request to `https://api.intercom.io/help_center/collections`. Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `I
 - [POST /help_center/collections](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/createcollection.md): You can create a new collection by making a POST request to `https://api.intercom.io/help_center/collections`. Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `In
 - [GET /help_center/collections/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/retrievecollection.md): You can fetch the details of a single collection by making a GET request to `https://api.intercom.io/help_center/collections/<id>`. Requires the `read_articles_scope` or `create_update_articles` OAuth
 - [PUT /help_center/collections/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/updatecollection.md): You can update the details of a single collection by making a PUT request to `https://api.intercom.io/help_center/collections/<id>`. `help_center_id` is checked but never applied. It must match the he
 - [DELETE /help_center/collections/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/deletecollection.md): You can delete a single collection by making a DELETE request to `https://api.intercom.io/help_center/collections/<id>`. Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Pr
 - [GET /help_center/help_centers/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/retrievehelpcenter.md): You can fetch the details of a single Help Center by making a GET request to `https://api.intercom.io/help_center/help_centers/<id>`. Requires the `read_articles_scope` or `create_update_articles` OAu
 - [GET /help_center/help_centers](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/help-center/listhelpcenters.md): You can list all Help Centers by making a GET request to `https://api.intercom.io/help_center/help_centers`. Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-V
## Identity Verification Secrets

 - [Identity Verification Secret](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/identity-verification-secrets/identity_verification_secret.md): Schema: #/components/schemas/identity_verification_secret
 - [Identity Verification Secret (with material)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/identity-verification-secrets/identity_verification_secret_with_material.md): Schema: #/components/schemas/identity_verification_secret_with_material
 - [GET /secure_mode_secrets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/identity-verification-secrets/listidentityverificationsecrets.md): Returns the identity verification secrets configured for your workspace. Each entry includes metadata only — the HMAC signing material itself is **never** returned by this endpoint. The raw secret is
 - [POST /secure_mode_secrets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/identity-verification-secrets/createidentityverificationsecret.md): Creates a new identity verification secret for your workspace. Intercom generates a 256-bit, cryptographically random value server-side and returns it once in the response. **This is the only opportun
 - [DELETE /secure_mode_secrets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/identity-verification-secrets/deleteidentityverificationsecret.md): Soft-deletes an identity verification secret. After deletion, any `user_hash` values signed with that secret will no longer verify — Messenger sessions depending on it will be rejected on their next r
## Internal Articles

 - [Internal Articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/internal_article_list_item.md): Schema: #/components/schemas/internal_article_list_item
 - [Internal Article Search Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/internal_article_search_response.md): Schema: #/components/schemas/internal_article_search_response
 - [GET /internal_articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/listinternalarticles.md): You can fetch a list of all internal articles by making a GET request to `https://api.intercom.io/internal_articles`. Requires the `read_articles_scope` or `read_write_articles_scope` OAuth scope.
 - [POST /internal_articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/createinternalarticle.md): You can create a new internal article by making a POST request to `https://api.intercom.io/internal_articles`. Requires the `read_write_articles_scope` OAuth scope.
 - [GET /internal_articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/retrieveinternalarticle.md): You can fetch the details of a single internal article by making a GET request to `https://api.intercom.io/internal_articles/<id>`. Requires the `read_articles_scope` or `read_write_articles_scope` OA
 - [PUT /internal_articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/updateinternalarticle.md): You can update the details of a single internal article by making a PUT request to `https://api.intercom.io/internal_articles/<id>`. Fields you leave out keep their current values. Requires the `read_
 - [DELETE /internal_articles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/deleteinternalarticle.md): You can delete a single internal article by making a DELETE request to `https://api.intercom.io/internal_articles/<id>`. Requires the `read_write_articles_scope` OAuth scope.
 - [POST /internal_articles/{internal_article_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/attachtagtointernalarticle.md): Apply an existing tag to an internal article. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have t
 - [DELETE /internal_articles/{internal_article_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/detachtagfrominternalarticle.md): Remove a tag from an internal article. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission.
 - [GET /internal_articles/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/internal-articles/searchinternalarticles.md): You can search for internal articles by making a GET request to `https://api.intercom.io/internal_articles/search`. Requires the `read_write_articles_scope` OAuth scope.
## IP Allowlist

 - [GET /ip_allowlist](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ip-allowlist/getipallowlist.md): Retrieve the current IP allowlist configuration for the workspace. Requires the `manage_ip_allowlist` OAuth scope.
 - [PUT /ip_allowlist](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ip-allowlist/updateipallowlist.md): Update the IP allowlist configuration for the workspace. Both `enabled` and `ip_allowlist` are optional. A field you omit is left unchanged, and a request with neither returns the current settings wit
## Jobs

 - [Jobs](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/jobs/jobs.md): Schema: #/components/schemas/jobs
 - [GET /jobs/status/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/jobs/jobsstatus.md): Retrieve the status of job execution. `resource_id` and `resource_url` are returned only once `status` is `success`. While the job is `pending` or `failed` both keys are left out of the response rathe
## Macros

 - [Macro](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/macro.md): Schema: #/components/schemas/macro
 - [Macro Action](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/macro_action.md): Schema: #/components/schemas/macro_action
 - [Macro Block](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/macro_block.md): Schema: #/components/schemas/macro_block
 - [Macro List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/macro_list.md): Schema: #/components/schemas/macro_list
 - [GET /macros](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/listmacros.md): You can fetch a list of all macros (saved replies) in your workspace for use in automating responses. The macros are returned in descending order by updated_at. **Pagination** This endpoint uses curso
 - [POST /macros](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/createmacro.md): You can create a macro in your workspace, choose who can see it, and add actions that run on the conversation when a teammate uses it. Send the content as either `body` or `blocks`, not both. `body` t
 - [GET /macros/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/macros/getmacro.md): You can fetch a single macro (saved reply) by its ID. The macro will only be returned if it is visible to the authenticated user based on its visibility settings. **Visibility Rules** A macro is retur
## Messages

 - [Message](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/messages/message.md): Schema: #/components/schemas/message
 - [POST /messages](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/messages/createmessage.md): You can create a message that has been initiated by an admin. The conversation can be either an in-app message, an email, sms or whatsapp. > 🚧 Sending for visitors There can be a short delay between
 - [GET /messages/status](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/messages/getwhatsappmessagestatus.md): Retrieves statuses of messages sent from the Outbound module. Currently, this API only supports WhatsApp messages. This endpoint returns paginated status events for WhatsApp messages sent via the Ou
 - [GET /messages/whatsapp/status](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/messages/retrievewhatsappmessagestatus.md): Retrieves the delivery status of a specific WhatsApp message by its message ID. Returns the current status, conversation details, and any error information if the message failed to deliver.
## News

 - [News Item](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/news_item.md): Schema: #/components/schemas/news_item
 - [Newsfeed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/newsfeed.md): Schema: #/components/schemas/newsfeed
 - [Newsfeed Assignment](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/newsfeed_assignment.md): Schema: #/components/schemas/newsfeed_assignment
 - [GET /news/news_items](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/listnewsitems.md): You can fetch a list of all news items News items are returned newest first, by creation date. Requires the `read_news_scope` or `read_write_news_scope` OAuth scope.
 - [POST /news/news_items](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/createnewsitem.md): You can create a news item Requires the `read_write_news_scope` OAuth scope.
 - [GET /news/news_items/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/retrievenewsitem.md): You can fetch the details of a single news item. Requires the `read_news_scope` or `read_write_news_scope` OAuth scope.
 - [PUT /news/news_items/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/updatenewsitem.md): You can update a news item. You can also send this request with `PATCH`; it behaves the same as `PUT`. Every field you leave out keeps its current value, including `labels`, `newsfeed_assignments` and
 - [DELETE /news/news_items/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/deletenewsitem.md): You can delete a single news item. Requires the `read_write_news_scope` OAuth scope.
 - [GET /news/newsfeeds/{id}/items](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/listlivenewsfeeditems.md): You can fetch a list of all news items that are live on a given newsfeed News items are returned most recently published first. Requires the `read_news_scope` or `read_write_news_scope` OAuth scope.
 - [GET /news/newsfeeds](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/listnewsfeeds.md): You can fetch a list of all newsfeeds Newsfeeds are returned newest first, by creation date. Requires the `read_news_scope` or `read_write_news_scope` OAuth scope.
 - [GET /news/newsfeeds/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/news/retrievenewsfeed.md): You can fetch the details of a single newsfeed Requires the `read_news_scope` or `read_write_news_scope` OAuth scope.
## Notes

 - [Note](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/note.md): Schema: #/components/schemas/note
 - [Company Note](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/company_note.md): Schema: #/components/schemas/company_note
 - [GET /companies/{company_id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/listcompanynotes.md): You can fetch a list of notes that are associated to a company. Requires the `read_users_companies` OAuth scope.
 - [POST /companies/{company_id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/createcompanynote.md): You can add a note to a single company. Requires the `write_users_companies` OAuth scope.
 - [GET /contacts/{id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/listnotes.md): You can fetch a list of notes that are associated to a contact. Requires the `read_users_companies` or `read_write_users` OAuth scope.
 - [POST /contacts/{id}/notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/createnote.md): You can add a note to a single contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [GET /notes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/retrievenote.md): You can fetch the details of a single note.
 - [DELETE /notes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/notes/deletenote.md): You can delete a single contact or company note. Notes of other kinds cannot be deleted through the API. Requires the `write_users_companies` OAuth scope.
## Office Hours

 - [Office Hours Time Interval](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/office_hours_time_interval.md): Schema: #/components/schemas/office_hours_time_interval
 - [Office Hours Schedule](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/office_hours_schedule.md): Schema: #/components/schemas/office_hours_schedule
 - [Office Hours Exception](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/office_hours_exception.md): Schema: #/components/schemas/office_hours_exception
 - [GET /office_hours_schedules](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/listofficehoursschedules.md): You can fetch a list of all office hours schedules for the workspace.
 - [POST /office_hours_schedules](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/createofficehoursschedule.md): You can create a new office hours schedule for the workspace.
 - [GET /office_hours_schedules/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/getofficehoursschedule.md): You can fetch the details of a single office hours schedule.
 - [PUT /office_hours_schedules/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/updateofficehoursschedule.md): You can update an existing office hours schedule.
 - [DELETE /office_hours_schedules/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/deleteofficehoursschedule.md): You can delete a single office hours schedule. The workspace's default schedule can't be deleted.
 - [GET /office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/listofficehoursexceptions.md): You can fetch a list of all exceptions for an office hours schedule, ordered by date with the earliest first.
 - [POST /office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/createofficehoursexception.md): You can create an exception for an office hours schedule. Use `closed` to mark the day closed (omit `time_intervals`) or `custom_hours` to supply replacement intervals.
 - [GET /office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/getofficehoursexception.md): You can fetch the details of a single office hours exception.
 - [PUT /office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/updateofficehoursexception.md): You can update an existing office hours exception.
 - [DELETE /office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/office-hours/deleteofficehoursexception.md): You can delete a single office hours exception.
## Procedures

 - [Collect Agent Input Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/procedures/collect_agent_input_request.md): Schema: #/components/schemas/collect_agent_input_request
 - [POST /procedures/{conversation_id}/collect_agent_input](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/procedures/collectprocedureagentinput.md): Submit human-collected input to a Fin Procedure that is paused at a Human in the Loop (HITL) step. When a procedure reaches a HITL step with the API channel enabled, Intercom sends a `procedure.hitl_n
## Reporting Data Export

 - [POST /export/reporting_data/enqueue](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/reporting-data-export/paths/~1export~1reporting_data~1enqueue/post.md): For the **conversation** dataset, from API version 2.16 this export returns all conversations, including those that never received a user reply. Earlier versions return only conversations that receive
 - [GET /export/reporting_data/{job_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/reporting-data-export/paths/~1export~1reporting_data~1%7Bjob_identifier%7D/get.md): Requires the `export_reporting_data` OAuth scope.
 - [GET /export/reporting_data/get_datasets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/reporting-data-export/paths/~1export~1reporting_data~1get_datasets/get.md): Requires the `export_reporting_data` or `read_reporting_datasets` OAuth scope.
 - [GET /download/reporting_data/{job_identifier}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/reporting-data-export/paths/~1download~1reporting_data~1%7Bjob_identifier%7D/get.md): Download the data from a completed reporting data export job. > Octet header required You will have to specify the header Accept: `application/octet-stream` when hitting this endpoint. Requires the `
## Roles

 - [Role](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/roles/role.md): Schema: #/components/schemas/role
 - [Role List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/roles/role_list.md): Schema: #/components/schemas/role_list
 - [GET /roles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/roles/listroles.md): You can fetch a list of all roles in the workspace. Roles define what a teammate can do in a workspace. The teammates endpoint returns the role a teammate holds, but only the roles that are currently
 - [GET /roles/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/roles/retrieverole.md): You can fetch the details of a single role by its id, including its description, which the teammates endpoint does not return.
## Segments

 - [Segment](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/segments/segment.md): Schema: #/components/schemas/segment
 - [GET /contacts/{contact_id}/segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/segments/listsegmentsforacontact.md): You can fetch a list of segments that are associated to a contact. Requires the `read_users_companies` or `read_write_users` OAuth scope.
 - [GET /segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/segments/listsegments.md): You can fetch a list of all segments. Segment names are returned HTML-escaped, for example `&` as `&amp;`. Requires the `read_users_companies` or `write_users_companies` OAuth scope.
 - [GET /segments/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/segments/retrievesegment.md): You can fetch the details of a single segment. The segment name is returned HTML-escaped, for example `&` as `&amp;`. Requires the `read_users_companies` or `write_users_companies` OAuth scope.
## SLA Rules

 - [SLA Rule](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/sla-rules/sla_rule.md): Schema: #/components/schemas/sla_rule
 - [SLA Rule List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/sla-rules/sla_rule_list.md): Schema: #/components/schemas/sla_rule_list
 - [GET /sla_rules](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/sla-rules/listslarules.md): You can fetch a list of all SLA rules for the workspace. The list is not paginated and is ordered by `id`, lowest first. It includes archived SLA rules; deleted SLA rules are not returned. Requires th
 - [GET /sla_rules/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/sla-rules/getslarule.md): You can fetch the details of a single SLA rule, including archived SLA rules. Requires the `read_conversations` OAuth scope.
## Subscription Types

 - [Subscription Types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/subscription_type.md): Schema: #/components/schemas/subscription_type
 - [GET /contacts/{contact_id}/subscriptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/listsubscriptionsforacontact.md): You can fetch a list of subscription types that are attached to a contact. These can be subscriptions that a user has 'opted-in' to or has 'opted-out' from, depending on the subscription type. This wi
 - [POST /contacts/{contact_id}/subscriptions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/attachsubscriptiontypetocontact.md): You can add a specific subscription to a contact. In Intercom, we have two different subscription types based on user consent - opt-out and opt-in: 1.Attaching a contact to an opt-out subscription typ
 - [DELETE /contacts/{contact_id}/subscriptions/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/detachsubscriptiontypetocontact.md): You can remove a specific subscription from a contact. This will return a subscription type model for the subscription type that was removed from the contact. Requires the `read_write_users` or `write
 - [GET /subscription_types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/listsubscriptiontypes.md): You can list all subscription types. A list of subscription type objects will be returned. Requires the `read_users_companies` OAuth scope.
 - [GET /subscription_types/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/subscription-types/getsubscriptiontype.md): You can fetch the details of a single subscription type by making a GET request to `https://api.intercom.io/subscription_types/<id>`. Requires the `read_users_companies` OAuth scope.
## Switch

 - [POST /phone_call_redirects](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/switch/createphoneswitch.md): You can use the API to deflect phone calls to the Intercom Messenger. Calling this endpoint will send an SMS with a link to the Messenger to the phone number specified. If custom attributes are speci
## Tags

 - [Tag](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/tag.md): Schema: #/components/schemas/tag
 - [Tag](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/tag_basic.md): Schema: #/components/schemas/tag_basic
 - [POST /ai/external_pages/{external_page_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtoexternalpage.md): Apply an existing tag to an external page. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the
 - [DELETE /ai/external_pages/{external_page_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromexternalpage.md): Remove a tag from an external page. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Pag
 - [POST /articles/{article_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtoarticle.md): Apply an existing tag to an article. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the `manag
 - [DELETE /articles/{article_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromarticle.md): Remove a tag from an article. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Requires
 - [POST /internal_articles/{internal_article_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtointernalarticle.md): Apply an existing tag to an internal article. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have t
 - [DELETE /internal_articles/{internal_article_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfrominternalarticle.md): Remove a tag from an internal article. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission.
 - [GET /contacts/{contact_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/listtagsforacontact.md): You can fetch a list of all tags that are attached to a specific contact.
 - [POST /contacts/{contact_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtocontact.md): You can tag a specific contact. This will return a tag object for the tag that was added to the contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [DELETE /contacts/{contact_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromcontact.md): You can remove tag from a specific contact. This will return a tag object for the tag that was removed from the contact. Requires the `read_write_users` or `write_users_companies` OAuth scope.
 - [POST /content_snippets/{content_snippet_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtocontentsnippet.md): Apply an existing tag to a content snippet. Returns the tag that was applied. The tag must already exist in the workspace (create tags with the Tags API), and the authenticating teammate must have the
 - [DELETE /content_snippets/{content_snippet_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromcontentsnippet.md): Remove a tag from a content snippet. Returns the tag that was removed, with null `applied_at` and `applied_by`. The authenticating teammate must have the `manage_knowledge_base_content` permission. Re
 - [POST /conversations/{conversation_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtoconversation.md): You can tag a specific conversation. This will return a tag object for the tag that was added to the conversation. If the conversation is a ticket, the access token must include the `write_tickets` sc
 - [DELETE /conversations/{conversation_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromconversation.md): You can remove tag from a specific conversation. This will return a tag object for the tag that was removed from the conversation. If the conversation is a ticket, the access token must include the `w
 - [GET /tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/listtags.md): You can fetch a list of all tags for a given workspace. Passing `id` returns that one tag object instead of a list. Passing `taggable_type` returns a list of the tags applied to a single contact or co
 - [POST /tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/createtag.md): You can use this endpoint to perform the following operations: **1. Create a new tag:** You can create a new tag by passing in the tag name as specified in "Create or Update Tag Request Payload" descr
 - [GET /tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/findtag.md): You can fetch the details of tags that are on the workspace by their id. This will return a tag object. Requires the `read_tags` or `read_users_companies` OAuth scope.
 - [DELETE /tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/deletetag.md): You can delete the details of tags that are on the workspace by passing in the id. Requires the `write_tags` or `write_users_companies` OAuth scope.
 - [PUT /tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/updatetag.md): You can archive or unarchive a tag by passing in its id. Archived tags are still returned by `GET /tags`, with `archived` set to `true`. You can't archive a tag that is still in use elsewhere in your
 - [POST /tickets/{ticket_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/attachtagtoticket.md): You can tag a specific ticket. This will return a tag object for the tag that was added to the ticket.
 - [DELETE /tickets/{ticket_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tags/detachtagfromticket.md): You can remove tag from a specific ticket. This will return a tag object for the tag that was removed from the ticket.
## Teams

 - [Team](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/team.md): Schema: #/components/schemas/team
 - [GET /teams/{team_id}/metrics](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/getteammetrics.md): Returns real-time activity metrics for admins in the specified team. For each admin, the response includes counts of open, idle, and snoozed conversations. This endpoint requires the `realtime_monitor
 - [GET /teams/{team_id}/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/retrieveteamofficehours.md): You can retrieve the team's linked office hours schedule, or the workspace default if the team has no schedule of its own. The team must belong to your workspace. An unknown, malformed, or other-works
 - [PUT /teams/{team_id}/office_hours](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/updateteamofficehours.md): You can assign an office hours schedule to a team or set `office_hours_schedule_id` to `null` to remove the team's own schedule so it uses the workspace default. The field is required, even when its v
 - [GET /teams](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/listteams.md): This will return a list of team objects for the App.
 - [GET /teams/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/retrieveteam.md): You can fetch the details of a single team, containing an array of admins that belong to this team.
 - [PUT /teams/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/teams/updateteammembers.md): You can replace the set of teammates who belong to a team. Send the full list of teammates the team should end up with — any teammate currently on the team and missing from the list is removed. This m
## Ticket States

 - [GET /ticket_states](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-states/listticketstates.md): You can get a list of all ticket states for a workspace. The list includes archived ticket states; check `archived` on each one.
## Ticket Type Attributes

 - [POST /ticket_types/{ticket_type_id}/attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-type-attributes/createtickettypeattribute.md): You can create a new attribute for a ticket type.
 - [PUT /ticket_types/{ticket_type_id}/attributes/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-type-attributes/updatetickettypeattribute.md): You can update an existing attribute for a ticket type.
## Ticket Types

 - [GET /ticket_types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-types/listtickettypes.md): You can get a list of all ticket types for a workspace. The list includes archived ticket types and ticket types that Intercom creates itself.
 - [POST /ticket_types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-types/createtickettype.md): You can create a new ticket type. > 📘 Creating ticket types. Every ticket type will be created with two default attributes: *default_title* and *default_description*. For the `icon` propery, use an e
 - [GET /ticket_types/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-types/gettickettype.md): You can fetch the details of a single ticket type. Archived ticket types are returned as well.
 - [PUT /ticket_types/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/ticket-types/updatetickettype.md): You can update a ticket type. > 📘 Updating a ticket type. For the `icon` propery, use an emoji from [Twemoji Cheatsheet](https://twemoji-cheatsheet.vercel.app/)
## Tickets

 - [Ticket](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket.md): Schema: #/components/schemas/ticket
 - [Contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket_contacts.md): Schema: #/components/schemas/ticket_contacts
 - [Ticket Part](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket_part.md): Schema: #/components/schemas/ticket_part
 - [Ticket State](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket_state.md): Schema: #/components/schemas/ticket_state
 - [Ticket State](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket_state_detailed.md): Schema: #/components/schemas/ticket_state_detailed
 - [Ticket Type](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/ticket_type.md): Schema: #/components/schemas/ticket_type
 - [POST /tickets/{id}/reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/replyticket.md): You can reply to a ticket with a message from an admin or on behalf of a contact, or with a note for admins.
 - [POST /tickets/{ticket_id}/tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/attachtagtoticket.md): You can tag a specific ticket. This will return a tag object for the tag that was added to the ticket.
 - [DELETE /tickets/{ticket_id}/tags/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/detachtagfromticket.md): You can remove tag from a specific ticket. This will return a tag object for the tag that was removed from the ticket.
 - [POST /tickets/{ticket_id}/linked_conversations](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/linkconversationtoticket.md): Link a conversation to an existing tracker ticket. The conversation can be a regular conversation or one that has been converted into a customer ticket. Use this when related conversations surface aft
 - [DELETE /tickets/{ticket_id}/linked_conversations/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/unlinkconversationfromticket.md): Unlink a conversation (or converted customer ticket) from a tracker ticket it is currently linked to. The ticket in the path must be a tracker ticket. This returns the conversation that was unlinked.
 - [POST /tickets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/createticket.md): You can create a new ticket.
 - [POST /tickets/enqueue](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/enqueuecreateticket.md): Enqueues ticket creation for asynchronous processing, returning if the job was enqueued successfully to be processed. We attempt to perform a best-effort validation on inputs before tasks are enqueued
 - [PUT /tickets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/updateticket.md): You can update a ticket.
 - [GET /tickets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/getticket.md): You can fetch the details of a single ticket.
 - [DELETE /tickets/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/deleteticket.md): Deleting a ticket is permanent and cannot be reversed. Deleting a ticket permanently removes it from the inbox. All sensitive data is deleted, including admin and user replies, ticket attributes, uplo
 - [POST /tickets/{ticket_id}/change_type](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/changetickettype.md): You can change the type of a ticket. The new ticket type must be in the same category as the current type. Attributes matching by name and type are automatically transferred from the old type; values
 - [POST /tickets/search](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/tickets/searchtickets.md): You can search for multiple tickets by the value of their attributes in order to fetch exactly which ones you want. To search for tickets, you send a `POST` request to `https://api.intercom.io/tickets
## Visitors

 - [PUT /visitors](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/visitors/updatevisitor.md): Sending a PUT request to `/visitors` will result in an update of an existing Visitor. **Option 1.** You can update a visitor by passing in the `user_id` of the visitor in the Request body. **Option 2.
 - [GET /visitors](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/visitors/retrievevisitorwithuserid.md): You can fetch the details of a single visitor. Requires the `read_single_user`, `read_users_companies` or `read_write_users` OAuth scope.
 - [POST /visitors/convert](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/visitors/convertvisitor.md): You can merge a Visitor to a Contact of role type `lead` or `user`. > 📘 What happens upon a visitor being converted? If the User exists, then the Visitor will be merged into it, the Visitor deleted a
## Workflows

 - [GET /export/workflows/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/workflows/exportworkflow.md): Export a workflow configuration by its ID. This endpoint returns the complete workflow definition including its steps, targeting rules, and attributes. The `id` in the path is the workflow's ruleset I
## Models

 - [Office Hours Schedule List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/office_hours_schedule_list.md): Schema: #/components/schemas/office_hours_schedule_list
 - [Teammate Office Hours List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_office_hours_list.md): Schema: #/components/schemas/admin_office_hours_list
 - [Paginated Teammate Office Hours List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_office_hours_paginated_list.md): Schema: #/components/schemas/admin_office_hours_paginated_list
 - [Update Office Hours Assignment Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_office_hours_assignment_request.md): Schema: #/components/schemas/update_office_hours_assignment_request
 - [Bulk Update Teammate Office Hours Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_update_admin_office_hours_request.md): Schema: #/components/schemas/bulk_update_admin_office_hours_request
 - [Office Hours Exception List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/office_hours_exception_list.md): Schema: #/components/schemas/office_hours_exception_list
 - [Create Office Hours Schedule Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_office_hours_schedule_request.md): Schema: #/components/schemas/create_office_hours_schedule_request
 - [Update Office Hours Schedule Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_office_hours_schedule_request.md): Schema: #/components/schemas/update_office_hours_schedule_request
 - [Create Office Hours Exception Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_office_hours_exception_request.md): Schema: #/components/schemas/create_office_hours_exception_request
 - [Update Office Hours Exception Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_office_hours_exception_request.md): Schema: #/components/schemas/update_office_hours_exception_request
 - [datetime](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/datetime.md): Schema: #/components/schemas/datetime
 - [Activity Log](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/activity_log.md): Schema: #/components/schemas/activity_log
 - [Paginated Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/activity_log_list.md): Schema: #/components/schemas/activity_log_list
 - [Activity Log Metadata](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/activity_log_metadata.md): Schema: #/components/schemas/activity_log_metadata
 - [Addressable List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/addressable_list.md): Schema: #/components/schemas/addressable_list
 - [Admins](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_list.md): Schema: #/components/schemas/admin_list
 - [Admin Priority Level](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_priority_level.md): Schema: #/components/schemas/admin_priority_level
 - [Admin Priority Level Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_priority_level_request.md): Schema: #/components/schemas/admin_priority_level_request
 - [Admin Reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_reply_conversation_request.md): Schema: #/components/schemas/admin_reply_conversation_request
 - [Bot Reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bot_reply_conversation_request.md): Schema: #/components/schemas/bot_reply_conversation_request
 - [Admin Reply on ticket](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_reply_ticket_request.md): Schema: #/components/schemas/admin_reply_ticket_request
 - [Admin](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/admin_with_app.md): Schema: #/components/schemas/admin_with_app
 - [AI Topic and Subtopic](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ai_topic_subtopic.md): Schema: #/components/schemas/ai_topic_subtopic
 - [App](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/app.md): Schema: #/components/schemas/app
 - [Audience List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/audience_list.md): Schema: #/components/schemas/audience_list
 - [Create Audience Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/audience_create_request.md): Schema: #/components/schemas/audience_create_request
 - [Update Audience Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/audience_update_request.md): Schema: #/components/schemas/audience_update_request
 - [Predicate](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/predicate.md): Schema: #/components/schemas/predicate
 - [Article Content](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/article_content.md): Schema: #/components/schemas/article_content
 - [Internal Articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/internal_article_list.md): Schema: #/components/schemas/internal_article_list
 - [Deleted Folder Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_folder_object.md): Schema: #/components/schemas/deleted_folder_object
 - [Articles](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/article_list.md): Schema: #/components/schemas/article_list
 - [Article Statistics](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/article_statistics.md): Schema: #/components/schemas/article_statistics
 - [Article Translated Content](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/article_translated_content.md): Schema: #/components/schemas/article_translated_content
 - [Article Versions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/article_version_list.md): Schema: #/components/schemas/article_version_list
 - [Assign Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/assign_conversation_request.md): Schema: #/components/schemas/assign_conversation_request
 - [Attach Contact To Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/attach_contact_to_conversation_request.md): Schema: #/components/schemas/attach_contact_to_conversation_request
 - [Conversation Participants Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_participants_response.md): Schema: #/components/schemas/conversation_participants_response
 - [team_metric](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_metric.md): Schema: #/components/schemas/team_metric
 - [team_metric_list](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_metric_list.md): Schema: #/components/schemas/team_metric_list
 - [Auth Token List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/auth_token_list.md): Schema: #/components/schemas/auth_token_list
 - [away_status_reason](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/away_status_reason.md): Schema: #/components/schemas/away_status_reason
 - [Away Status Reasons](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/away_status_reason_list.md): Schema: #/components/schemas/away_status_reason_list
 - [Change Ticket Type Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/change_ticket_type_request.md): Schema: #/components/schemas/change_ticket_type_request
 - [Close Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/close_conversation_request.md): Schema: #/components/schemas/close_conversation_request
 - [Help Center Redirects](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/help_center_redirect_list.md): Schema: #/components/schemas/help_center_redirect_list
 - [Create Help Center Redirect Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_help_center_redirect_request.md): Schema: #/components/schemas/create_help_center_redirect_request
 - [Deleted Help Center Redirect Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_help_center_redirect_object.md): Schema: #/components/schemas/deleted_help_center_redirect_object
 - [Collections](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/collection_list.md): Schema: #/components/schemas/collection_list
 - [Bulk Create Companies Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_create_companies_request.md): Schema: #/components/schemas/bulk_create_companies_request
 - [Bulk Delete Companies Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_delete_companies_request.md): Schema: #/components/schemas/bulk_delete_companies_request
 - [Bulk Update Companies Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_update_companies_request.md): Schema: #/components/schemas/bulk_update_companies_request
 - [Bulk Create Contacts Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_create_contacts_request.md): Schema: #/components/schemas/bulk_create_contacts_request
 - [Bulk Delete Contacts Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_delete_contacts_request.md): Schema: #/components/schemas/bulk_delete_contacts_request
 - [Bulk Update Contacts Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/bulk_update_contacts_request.md): Schema: #/components/schemas/bulk_update_contacts_request
 - [Company Attached Contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_attached_contacts.md): Schema: #/components/schemas/company_attached_contacts
 - [Company Attached Segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_attached_segments.md): Schema: #/components/schemas/company_attached_segments
 - [Companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_list.md): Schema: #/components/schemas/company_list
 - [Company Search Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_search_response.md): Schema: #/components/schemas/company_search_response
 - [Company Scroll](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_scroll.md): Schema: #/components/schemas/company_scroll
 - [Company Users](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_user_list.md): Schema: #/components/schemas/company_user_list
 - [Merge History Item](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_history_item.md): Schema: #/components/schemas/merge_history_item
 - [Merge History List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_history_list.md): Schema: #/components/schemas/merge_history_list
 - [Contact Attached Companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_attached_companies.md): Schema: #/components/schemas/contact_attached_companies
 - [Contact companies](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_companies.md): Schema: #/components/schemas/contact_companies
 - [Company Data](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_data.md): Schema: #/components/schemas/company_data
 - [Contact Deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_deleted.md): Schema: #/components/schemas/contact_deleted
 - [Contact Activity](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_activity.md): Schema: #/components/schemas/contact_activity
 - [Contact Activity List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_activity_list.md): Schema: #/components/schemas/contact_activity_list
 - [Contact List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_list.md): Schema: #/components/schemas/contact_list
 - [Contact Location](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_location.md): Schema: #/components/schemas/contact_location
 - [Contact notes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_notes.md): Schema: #/components/schemas/contact_notes
 - [Contact Reference](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reference.md): Schema: #/components/schemas/contact_reference
 - [Contact Reply Base Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_base_request.md): Schema: #/components/schemas/contact_reply_base_request
 - [Contact Reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_conversation_request.md): Schema: #/components/schemas/contact_reply_conversation_request
 - [Email](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_email_request.md): Schema: #/components/schemas/contact_reply_email_request
 - [Intercom User ID](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_intercom_user_id_request.md): Schema: #/components/schemas/contact_reply_intercom_user_id_request
 - [Email](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_ticket_email_request.md): Schema: #/components/schemas/contact_reply_ticket_email_request
 - [Intercom User ID](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_ticket_intercom_user_id_request.md): Schema: #/components/schemas/contact_reply_ticket_intercom_user_id_request
 - [Contact Reply on ticket](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_ticket_request.md): Schema: #/components/schemas/contact_reply_ticket_request
 - [User ID](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_ticket_user_id_request.md): Schema: #/components/schemas/contact_reply_ticket_user_id_request
 - [User ID](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_reply_user_id_request.md): Schema: #/components/schemas/contact_reply_user_id_request
 - [Contact search request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_search_request.md): Schema: #/components/schemas/contact_search_request
 - [Segments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_segments.md): Schema: #/components/schemas/contact_segments
 - [Social Profile](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_social_profiles.md): Schema: #/components/schemas/contact_social_profiles
 - [Contact Subscription Types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_subscription_types.md): Schema: #/components/schemas/contact_subscription_types
 - [Contact Tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_tags.md): Schema: #/components/schemas/contact_tags
 - [Contact Archived](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_archived.md): Schema: #/components/schemas/contact_archived
 - [Contact Unarchived](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_unarchived.md): Schema: #/components/schemas/contact_unarchived
 - [Deleted Contact](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_contact.md): Schema: #/components/schemas/deleted_contact
 - [Deleted Contact List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_contact_list.md): Schema: #/components/schemas/deleted_contact_list
 - [Contact Blocked](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/contact_blocked.md): Schema: #/components/schemas/contact_blocked
 - [Content Bulk Action Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_bulk_action_request.md): Schema: #/components/schemas/content_bulk_action_request
 - [Content Bulk Action Response Envelope](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_bulk_action_response.md): Schema: #/components/schemas/content_bulk_action_response
 - [Content Source List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_sources_list.md): Schema: #/components/schemas/content_sources_list
 - [Content Snippet List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_snippet_list.md): Schema: #/components/schemas/content_snippet_list
 - [Create Content Snippet Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_snippet_create_request.md): Schema: #/components/schemas/content_snippet_create_request
 - [Update Content Snippet Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/content_snippet_update_request.md): Schema: #/components/schemas/content_snippet_update_request
 - [Dynamic Content List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/dynamic_content_list.md): Schema: #/components/schemas/dynamic_content_list
 - [Dynamic Content Variation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/dynamic_content_variation_request.md): Schema: #/components/schemas/dynamic_content_variation_request
 - [Create Dynamic Content Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/dynamic_content_create_request.md): Schema: #/components/schemas/dynamic_content_create_request
 - [Update Dynamic Content Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/dynamic_content_update_request.md): Schema: #/components/schemas/dynamic_content_update_request
 - [Conversation Channel](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_channel.md): Schema: #/components/schemas/conversation_channel
 - [Conversation External Reference](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_external_reference.md): Schema: #/components/schemas/conversation_external_reference
 - [Conversation attachment files](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attachment_files.md): Schema: #/components/schemas/conversation_attachment_files
 - [Contacts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_contacts.md): Schema: #/components/schemas/conversation_contacts
 - [Conversation Deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_deleted.md): Schema: #/components/schemas/conversation_deleted
 - [Create conversation stream token request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_stream_token_request.md): Schema: #/components/schemas/create_conversation_stream_token_request
 - [Conversations](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_conversation_list.md): Schema: #/components/schemas/deleted_conversation_list
 - [First contact reply](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_first_contact_reply.md): Schema: #/components/schemas/conversation_first_contact_reply
 - [Conversation List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_list.md): Schema: #/components/schemas/conversation_list
 - [Conversation Part](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_part.md): Schema: #/components/schemas/conversation_part
 - [Conversation part author](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_part_author.md): Schema: #/components/schemas/conversation_part_author
 - [Conversation Parts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_parts.md): Schema: #/components/schemas/conversation_parts
 - [Conversation Part Metadata](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_part_metadata.md): Schema: #/components/schemas/conversation_part_metadata
 - [Conversation Rating](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_rating.md): Schema: #/components/schemas/conversation_rating
 - [Conversation response time](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_response_time.md): Schema: #/components/schemas/conversation_response_time
 - [Rate conversation request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/rate_conversation_request.md): Schema: #/components/schemas/rate_conversation_request
 - [Conversation source](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_source.md): Schema: #/components/schemas/conversation_source
 - [Conversation source author](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_source_author.md): Schema: #/components/schemas/conversation_source_author
 - [Conversation statistics](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_statistics.md): Schema: #/components/schemas/conversation_statistics
 - [Conversation teammates](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_teammates.md): Schema: #/components/schemas/conversation_teammates
 - [Convert Ticket Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/convert_conversation_to_ticket_request.md): Schema: #/components/schemas/convert_conversation_to_ticket_request
 - [Convert Visitor Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/convert_visitor_request.md): Schema: #/components/schemas/convert_visitor_request
 - [Create API Template Source Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_api_template_source_request.md): Schema: #/components/schemas/create_api_template_source_request
 - [Create Article Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_article_request.md): Schema: #/components/schemas/create_article_request
 - [Create Internal Article Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_internal_article_request.md): Schema: #/components/schemas/create_internal_article_request
 - [Create Collection Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_collection_request.md): Schema: #/components/schemas/create_collection_request
 - [Create Contact Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_contact_request.md): Schema: #/components/schemas/create_contact_request
 - [Create Content Import Source Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_content_import_source_request.md): Schema: #/components/schemas/create_content_import_source_request
 - [Create Conversation Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_request.md): Schema: #/components/schemas/create_conversation_request
 - [Create Data Attribute Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_data_attribute_request.md): Schema: #/components/schemas/create_data_attribute_request
 - [Create Data Event Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_data_event_request.md): Schema: #/components/schemas/create_data_event_request
 - [Create Data Event Summaries Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_data_event_summaries_request.md): Schema: #/components/schemas/create_data_event_summaries_request
 - [Create Data Export Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_data_exports_request.md): Schema: #/components/schemas/create_data_exports_request
 - [Create External Page Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_external_page_request.md): Schema: #/components/schemas/create_external_page_request
 - [Create Macro Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_macro_request.md): Schema: #/components/schemas/create_macro_request
 - [Create Message Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_message_request.md): Schema: #/components/schemas/create_message_request
 - [Recipient](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/recipient.md): Schema: #/components/schemas/recipient
 - [Create Or Update Company Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_or_update_company_request.md): Schema: #/components/schemas/create_or_update_company_request
 - [Update Company Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_company_request.md): Schema: #/components/schemas/update_company_request
 - [Create Or Update Custom Object Instance Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_or_update_custom_object_instance_request.md): Schema: #/components/schemas/create_or_update_custom_object_instance_request
 - [Update Tag Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_tag_request.md): Schema: #/components/schemas/update_tag_request
 - [Create or Update Tag Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_or_update_tag_request.md): Schema: #/components/schemas/create_or_update_tag_request
 - [Create Phone Switch Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_phone_switch_request.md): Schema: #/components/schemas/create_phone_switch_request
 - [Create Ticket Reply Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_ticket_reply_with_comment_request.md): Schema: #/components/schemas/create_ticket_reply_with_comment_request
 - [Create Ticket Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_ticket_request.md): Schema: #/components/schemas/create_ticket_request
 - [Create Ticket Type Attribute Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_ticket_type_attribute_request.md): Schema: #/components/schemas/create_ticket_type_attribute_request
 - [Create Ticket Type Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_ticket_type_request.md): Schema: #/components/schemas/create_ticket_type_request
 - [Cursor based pages](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/cursor_pages.md): Schema: #/components/schemas/cursor_pages
 - [Calls](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/call_list.md): Schema: #/components/schemas/call_list
 - [Custom Attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_attributes.md): Schema: #/components/schemas/custom_attributes
 - [Custom Attributes (write)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_attributes_request.md): Schema: #/components/schemas/custom_attributes_request
 - [CX Score reason](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/cx_score_reason.md): Schema: #/components/schemas/cx_score_reason
 - [Custom Object Instance Deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_object_instance_deleted.md): Schema: #/components/schemas/custom_object_instance_deleted
 - [Custom Object Instances](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_object_instance_list.md): Schema: #/components/schemas/custom_object_instance_list
 - [Custom Object Instance Not Found](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_object_instance_not_found.md): Schema: #/components/schemas/custom_object_instance_not_found
 - [customer_request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/customer_request.md): Schema: #/components/schemas/customer_request
 - [Data Attribute List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_attribute_list.md): Schema: #/components/schemas/data_attribute_list
 - [Conversation Attribute Base](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_base.md): Schema: #/components/schemas/conversation_attribute_base
 - [Conversation Attribute (String)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_string_type.md): Schema: #/components/schemas/conversation_attribute_string_type
 - [Conversation Attribute (Integer)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_integer_type.md): Schema: #/components/schemas/conversation_attribute_integer_type
 - [Conversation Attribute (List)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_list_type.md): Schema: #/components/schemas/conversation_attribute_list_type
 - [Conversation Attribute (Decimal)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_decimal_type.md): Schema: #/components/schemas/conversation_attribute_decimal_type
 - [Conversation Attribute (Boolean)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_boolean_type.md): Schema: #/components/schemas/conversation_attribute_boolean_type
 - [Conversation Attribute (Datetime)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_datetime_type.md): Schema: #/components/schemas/conversation_attribute_datetime_type
 - [Conversation Attribute (Relationship)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_relationship_type.md): Schema: #/components/schemas/conversation_attribute_relationship_type
 - [Conversation Attribute (Files)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_files_type.md): Schema: #/components/schemas/conversation_attribute_files_type
 - [Conversation Attribute List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_list.md): Schema: #/components/schemas/conversation_attribute_list
 - [Conversation Attribute Option](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_option.md): Schema: #/components/schemas/conversation_attribute_option
 - [Create Conversation Attribute Option Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_option_request.md): Schema: #/components/schemas/create_conversation_attribute_option_request
 - [Update Conversation Attribute Option Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_conversation_attribute_option_request.md): Schema: #/components/schemas/update_conversation_attribute_option_request
 - [Create Conversation Attribute Request Base](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_request_base.md): Schema: #/components/schemas/create_conversation_attribute_request_base
 - [Create Conversation Attribute Request (String)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_string_request.md): Schema: #/components/schemas/create_conversation_attribute_string_request
 - [Create Conversation Attribute Request (Integer)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_integer_request.md): Schema: #/components/schemas/create_conversation_attribute_integer_request
 - [Create Conversation Attribute Request (List)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_list_request.md): Schema: #/components/schemas/create_conversation_attribute_list_request
 - [Create Conversation Attribute Request (Decimal)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_decimal_request.md): Schema: #/components/schemas/create_conversation_attribute_decimal_request
 - [Create Conversation Attribute Request (Boolean)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_boolean_request.md): Schema: #/components/schemas/create_conversation_attribute_boolean_request
 - [Create Conversation Attribute Request (Datetime)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_datetime_request.md): Schema: #/components/schemas/create_conversation_attribute_datetime_request
 - [Create Conversation Attribute Request (Relationship)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_relationship_request.md): Schema: #/components/schemas/create_conversation_attribute_relationship_request
 - [Create Conversation Attribute Request (Files)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_files_request.md): Schema: #/components/schemas/create_conversation_attribute_files_request
 - [Create Conversation Attribute Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_conversation_attribute_request.md): Schema: #/components/schemas/create_conversation_attribute_request
 - [Update Conversation Attribute Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_conversation_attribute_request.md): Schema: #/components/schemas/update_conversation_attribute_request
 - [Create Data Connector Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_data_connector_request.md): Schema: #/components/schemas/create_data_connector_request
 - [Update Data Connector Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_data_connector_request.md): Schema: #/components/schemas/update_data_connector_request
 - [Data Connector Execution Result List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_connector_execution_result_list.md): Schema: #/components/schemas/data_connector_execution_result_list
 - [Data Connector List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_connector_list.md): Schema: #/components/schemas/data_connector_list
 - [Data Connector Version List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_connector_version_list.md): Schema: #/components/schemas/data_connector_version_list
 - [Update Data Connector Version Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_data_connector_version_request.md): Schema: #/components/schemas/update_data_connector_version_request
 - [Deleted Data Connector Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_data_connector_object.md): Schema: #/components/schemas/deleted_data_connector_object
 - [Data Event List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_event_list.md): Schema: #/components/schemas/data_event_list
 - [Data Event Summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_event_summary.md): Schema: #/components/schemas/data_event_summary
 - [Data Event Summary Item](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_event_summary_item.md): Schema: #/components/schemas/data_event_summary_item
 - [Data Export CSV](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/data_export_csv.md): Schema: #/components/schemas/data_export_csv
 - [Deleted Article Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_article_object.md): Schema: #/components/schemas/deleted_article_object
 - [Deleted Internal Article Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_internal_article_object.md): Schema: #/components/schemas/deleted_internal_article_object
 - [Deleted Collection Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_collection_object.md): Schema: #/components/schemas/deleted_collection_object
 - [Deleted Company Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_company_object.md): Schema: #/components/schemas/deleted_company_object
 - [Deleted Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_object.md): Schema: #/components/schemas/deleted_object
 - [Deleted Call Recording Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_call_recording_object.md): Schema: #/components/schemas/deleted_call_recording_object
 - [Deleted Note Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/deleted_note_object.md): Schema: #/components/schemas/deleted_note_object
 - [detach_contact_from_conversation_request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/detach_contact_from_conversation_request.md): Schema: #/components/schemas/detach_contact_from_conversation_request
 - [Ecommerce Catalog Upload Part Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_catalog_upload_part_response.md): Schema: #/components/schemas/ecommerce_catalog_upload_part_response
 - [Ecommerce Catalog Upload Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_catalog_upload_response.md): Schema: #/components/schemas/ecommerce_catalog_upload_response
 - [Ecommerce Catalog Variant](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_catalog_variant.md): Schema: #/components/schemas/ecommerce_catalog_variant
 - [Ecommerce Catalog Product](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_catalog_product.md): Schema: #/components/schemas/ecommerce_catalog_product
 - [Ecommerce Order Event Line Item](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_order_event_line_item.md): Schema: #/components/schemas/ecommerce_order_event_line_item
 - [Ecommerce Order Event Order](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_order_event_order.md): Schema: #/components/schemas/ecommerce_order_event_order
 - [Ecommerce Product Event Error](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_product_event_error.md): Schema: #/components/schemas/ecommerce_product_event_error
 - [Ecommerce Product Event Product](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_product_event_product.md): Schema: #/components/schemas/ecommerce_product_event_product
 - [Ecommerce Product Event Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_product_event_request.md): Schema: #/components/schemas/ecommerce_product_event_request
 - [Ecommerce Product Event Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ecommerce_product_event_response.md): Schema: #/components/schemas/ecommerce_product_event_response
 - [Email Address Header](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/email_address_header.md): Schema: #/components/schemas/email_address_header
 - [Email Message Metadata](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/email_message_metadata.md): Schema: #/components/schemas/email_message_metadata
 - [Email Message Metadata](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/source_email_message_metadata.md): Schema: #/components/schemas/source_email_message_metadata
 - [Part type - conversation_attribute_updated_by_workflow](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_updated_by_workflow.md): Schema: #/components/schemas/conversation_attribute_updated_by_workflow
 - [Part type - conversation_attribute_updated_by_admin](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_updated_by_admin.md): Schema: #/components/schemas/conversation_attribute_updated_by_admin
 - [Part type - conversation_attribute_updated_by_user](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_attribute_updated_by_user.md): Schema: #/components/schemas/conversation_attribute_updated_by_user
 - [Part type - custom_action_started](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_action_started.md): Schema: #/components/schemas/custom_action_started
 - [Part type - custom_action_finished](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/custom_action_finished.md): Schema: #/components/schemas/custom_action_finished
 - [Part type - operator_workflow_event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/operator_workflow_event.md): Schema: #/components/schemas/operator_workflow_event
 - [Part type - conversation_tags_updated](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_tags_updated.md): Schema: #/components/schemas/conversation_tags_updated
 - [Part type - snoozed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/snoozed.md): Schema: #/components/schemas/snoozed
 - [Part type - priority_changed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/priority_changed.md): Schema: #/components/schemas/priority_changed
 - [Part type - conversation_sla_applied_by_rule](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_applied_by_rule.md): Schema: #/components/schemas/conversation_sla_applied_by_rule
 - [Part type - conversation_sla_applied_by_workflow](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_applied_by_workflow.md): Schema: #/components/schemas/conversation_sla_applied_by_workflow
 - [Part type - conversation_sla_target_missed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_target_missed.md): Schema: #/components/schemas/conversation_sla_target_missed
 - [Part type - conversation_sla_paused](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_paused.md): Schema: #/components/schemas/conversation_sla_paused
 - [Part type - conversation_sla_unpaused](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_unpaused.md): Schema: #/components/schemas/conversation_sla_unpaused
 - [Part type - conversation_sla_removed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/conversation_sla_removed.md): Schema: #/components/schemas/conversation_sla_removed
 - [Part type - call_summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/call_summary.md): Schema: #/components/schemas/call_summary
 - [Part type - ai_agent_event (otp_email_verification_failed)](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ai_agent_event_otp_email_verification_failed.md): Schema: #/components/schemas/ai_agent_event_otp_email_verification_failed
 - [Part type - standalone_platform_handoff](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/standalone_platform_handoff.md): Schema: #/components/schemas/standalone_platform_handoff
 - [Event details of Workflow & actions](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/event_details.md): Schema: #/components/schemas/event_details
 - [Error](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/error.md): Schema: #/components/schemas/error
 - [Fin Task List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/fin_task_list.md): Schema: #/components/schemas/fin_task_list
 - [Create Fin Task Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_fin_task_request.md): Schema: #/components/schemas/create_fin_task_request
 - [Update Fin Task Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_fin_task_request.md): Schema: #/components/schemas/update_fin_task_request
 - [File](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/file_attribute.md): Schema: #/components/schemas/file_attribute
 - [Group Content](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/group_content.md): Schema: #/components/schemas/group_content
 - [Group Translated Content](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/group_translated_content.md): Schema: #/components/schemas/group_translated_content
 - [Granted Company List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/granted_company_list.md): Schema: #/components/schemas/granted_company_list
 - [Replace Granted Companies Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/replace_granted_companies_request.md): Schema: #/components/schemas/replace_granted_companies_request
 - [Handling Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/handling_event.md): Schema: #/components/schemas/handling_event
 - [Handling Event List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/handling_event_list.md): Schema: #/components/schemas/handling_event_list
 - [HITL Event](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/hitl_event.md): Schema: #/components/schemas/hitl_event
 - [HITL Event List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/hitl_event_list.md): Schema: #/components/schemas/hitl_event_list
 - [Side Conversation Summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/side_conversation_summary.md): Schema: #/components/schemas/side_conversation_summary
 - [Side Conversation List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/side_conversation_list.md): Schema: #/components/schemas/side_conversation_list
 - [Identity Verification Secrets](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/identity_verification_secret_list.md): Schema: #/components/schemas/identity_verification_secret_list
 - [Create Identity Verification Secret Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/create_identity_verification_secret_request.md): Schema: #/components/schemas/create_identity_verification_secret_request
 - [IP Allowlist](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ip_allowlist.md): Schema: #/components/schemas/ip_allowlist
 - [intercom_version](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/intercom_version.md): Schema: #/components/schemas/intercom_version
 - [Linked Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/linked_object.md): Schema: #/components/schemas/linked_object
 - [intercom_version_preview](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/intercom_version_preview.md): Schema: #/components/schemas/intercom_version_preview
 - [Linked Objects](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/linked_object_list.md): Schema: #/components/schemas/linked_object_list
 - [Merge contact data](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_contacts_request.md): Schema: #/components/schemas/merge_contacts_request
 - [Merge preview request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_request.md): Schema: #/components/schemas/merge_preview_request
 - [Merge preview response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_response.md): Schema: #/components/schemas/merge_preview_response
 - [Merge preview allowed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_allowed.md): Schema: #/components/schemas/merge_preview_allowed
 - [Merge preview not allowed](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_blocked.md): Schema: #/components/schemas/merge_preview_blocked
 - [Merge preview reason](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_reason.md): Schema: #/components/schemas/merge_preview_reason
 - [Merge preview summary](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_summary.md): Schema: #/components/schemas/merge_preview_summary
 - [Merge preview attribute changes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_attribute_changes.md): Schema: #/components/schemas/merge_preview_attribute_changes
 - [Merge preview attribute change](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_attribute_change.md): Schema: #/components/schemas/merge_preview_attribute_change
 - [Merge preview reassignments](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/merge_preview_reassignments.md): Schema: #/components/schemas/merge_preview_reassignments
 - [whatsapp_message_status_list](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/whatsapp_message_status_list.md): Schema: #/components/schemas/whatsapp_message_status_list
 - [whatsapp_message_status](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/whatsapp_message_status.md): Schema: #/components/schemas/whatsapp_message_status
 - [Multiple Filter Search Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/multiple_filter_search_request.md): Schema: #/components/schemas/multiple_filter_search_request
 - [Create News Item Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/news_item_request.md): Schema: #/components/schemas/news_item_request
 - [Update News Item Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_news_item_request.md): Schema: #/components/schemas/update_news_item_request
 - [Banner List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/banner_list.md): Schema: #/components/schemas/banner_list
 - [Paginated Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/note_list.md): Schema: #/components/schemas/note_list
 - [Open Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/open_conversation_request.md): Schema: #/components/schemas/open_conversation_request
 - [Pagination Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/pages_link.md): Schema: #/components/schemas/pages_link
 - [Paginated Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/paginated_response.md): Schema: #/components/schemas/paginated_response
 - [Part attachment](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/part_attachment.md): Schema: #/components/schemas/part_attachment
 - [Phone Switch](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/phone_switch.md): Schema: #/components/schemas/phone_switch
 - [Quick Reply Option](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/quick_reply_option.md): Schema: #/components/schemas/quick_reply_option
 - [Update Conversation Part Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_conversation_part_request.md): Schema: #/components/schemas/update_conversation_part_request
 - [redact_conversation_request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/redact_conversation_request.md): Schema: #/components/schemas/redact_conversation_request
 - [Reference](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/reference.md): Schema: #/components/schemas/reference
 - [reply_conversation_request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/reply_conversation_request.md): Schema: #/components/schemas/reply_conversation_request
 - [Search data](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/search_request.md): Schema: #/components/schemas/search_request
 - [Company search request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/company_search_request.md): Schema: #/components/schemas/company_search_request
 - [Segment List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/segment_list.md): Schema: #/components/schemas/segment_list
 - [Single Filter Search Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/single_filter_search_request.md): Schema: #/components/schemas/single_filter_search_request
 - [Applied SLA](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/sla_applied.md): Schema: #/components/schemas/sla_applied
 - [Snooze Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/snooze_conversation_request.md): Schema: #/components/schemas/snooze_conversation_request
 - [Social Profile](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/social_profile.md): Schema: #/components/schemas/social_profile
 - [Pagination: Starting After](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/starting_after_paging.md): Schema: #/components/schemas/starting_after_paging
 - [Subscription Types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/subscription_type_list.md): Schema: #/components/schemas/subscription_type_list
 - [Create or Update Tag Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/tag_create_response.md): Schema: #/components/schemas/tag_create_response
 - [Tag Company Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/tag_company_request.md): Schema: #/components/schemas/tag_company_request
 - [Tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/tag_list.md): Schema: #/components/schemas/tag_list
 - [Tag Users Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/tag_multiple_users_request.md): Schema: #/components/schemas/tag_multiple_users_request
 - [Tags](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/tags.md): Schema: #/components/schemas/tags
 - [Team Handling Segment](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_handling_segment.md): Schema: #/components/schemas/team_handling_segment
 - [Team Handling Segment List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_handling_segment_list.md): Schema: #/components/schemas/team_handling_segment_list
 - [Team List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_list.md): Schema: #/components/schemas/team_list
 - [Team Priority Level](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/team_priority_level.md): Schema: #/components/schemas/team_priority_level
 - [Teammate Reference](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/teammate_reference.md): Schema: #/components/schemas/teammate_reference
 - [Ticket Deleted](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_deleted.md): Schema: #/components/schemas/ticket_deleted
 - [Ticket Attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_custom_attributes.md): Schema: #/components/schemas/ticket_custom_attributes
 - [Ticket List](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_list.md): Schema: #/components/schemas/ticket_list
 - [Ticket part author](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_part_author.md): Schema: #/components/schemas/ticket_part_author
 - [Ticket Parts](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_parts.md): Schema: #/components/schemas/ticket_parts
 - [A Ticket Part representing a note, comment, or quick_reply on a ticket](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_reply.md): Schema: #/components/schemas/ticket_reply
 - [Ticket Attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_request_custom_attributes.md): Schema: #/components/schemas/ticket_request_custom_attributes
 - [Ticket States](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_state_list.md): Schema: #/components/schemas/ticket_state_list
 - [Ticket Type Attribute](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_type_attribute.md): Schema: #/components/schemas/ticket_type_attribute
 - [Ticket Type Attributes](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_type_attribute_list.md): Schema: #/components/schemas/ticket_type_attribute_list
 - [Ticket Types](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ticket_type_list.md): Schema: #/components/schemas/ticket_type_list
 - [Translation](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/translation.md): Schema: #/components/schemas/translation
 - [Untag Company Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/untag_company_request.md): Schema: #/components/schemas/untag_company_request
 - [Publish Article Draft Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/publish_article_draft_request.md): Schema: #/components/schemas/publish_article_draft_request
 - [Stage Article Draft Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/stage_article_draft_request_body.md): Schema: #/components/schemas/stage_article_draft_request_body
 - [Update Article Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_article_request.md): Schema: #/components/schemas/update_article_request
 - [Update Internal Article Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_internal_article_request.md): Schema: #/components/schemas/update_internal_article_request
 - [Update Collection Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_collection_request.md): Schema: #/components/schemas/update_collection_request
 - [Update Contact Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_contact_request.md): Schema: #/components/schemas/update_contact_request
 - [Update Content Import Source Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_content_import_source_request.md): Schema: #/components/schemas/update_content_import_source_request
 - [Update Conversation Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_conversation_request.md): Schema: #/components/schemas/update_conversation_request
 - [Update Data Attribute Request](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_data_attribute_request.md): Schema: #/components/schemas/update_data_attribute_request
 - [Update External Page Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_external_page_request.md): Schema: #/components/schemas/update_external_page_request
 - [Update Team Members Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_team_members_request.md): Schema: #/components/schemas/update_team_members_request
 - [Update Ticket Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_ticket_request.md): Schema: #/components/schemas/update_ticket_request
 - [Update Ticket Type Attribute Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_ticket_type_attribute_request.md): Schema: #/components/schemas/update_ticket_type_attribute_request
 - [Update Ticket Type Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_ticket_type_request.md): Schema: #/components/schemas/update_ticket_type_request
 - [Update Visitor Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/update_visitor_request.md): Schema: #/components/schemas/update_visitor_request
 - [Visitor](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/visitor.md): Schema: #/components/schemas/visitor
 - [Visitor Deleted Object](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/visitor_deleted_object.md): Schema: #/components/schemas/visitor_deleted_object
 - [Workflow Export](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/workflow_export.md): Schema: #/components/schemas/workflow_export
 - [AI Call Response](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/ai_call_response.md): Schema: #/components/schemas/ai_call_response
 - [Register Fin Voice Call Request Payload](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/models/register_fin_voice_call_request.md): Schema: #/components/schemas/register_fin_voice_call_request
## Folders

 - [Folder](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/folder.md): Schema: #/components/schemas/folder
 - [GET /folders](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/listfolders.md): You can fetch a list of all folders for organizing content by making a GET request to `https://api.intercom.io/folders`. Requires the `read_articles_scope` or `read_write_articles_scope` OAuth scope.
 - [POST /folders](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/createfolder.md): You can create a new folder for organizing content by making a POST request to `https://api.intercom.io/folders`. Requires the `read_write_articles_scope` OAuth scope.
 - [GET /folders/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/retrievefolder.md): You can fetch the details of a single folder by making a GET request to `https://api.intercom.io/folders/<id>`. Requires the `read_articles_scope` or `read_write_articles_scope` OAuth scope.
 - [PUT /folders/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/updatefolder.md): You can update a folder by making a PUT request to `https://api.intercom.io/folders/<id>`. Fields you leave out keep their current values. Send `parent_folder_id` as `null` to move the folder to the t
 - [DELETE /folders/{id}](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/folders/deletefolder.md): You can delete a folder (if it contains no content) by making a DELETE request to `https://api.intercom.io/folders/<id>`. Requires the `read_write_articles_scope` OAuth scope.
## WhatsApp

 - [GET /messages/status](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/whatsapp/getwhatsappmessagestatus.md): Retrieves statuses of messages sent from the Outbound module. Currently, this API only supports WhatsApp messages. This endpoint returns paginated status events for WhatsApp messages sent via the Ou
 - [GET /messages/whatsapp/status](https://developers.intercom.com/docs/references/preview/rest-api/api.intercom.io/whatsapp/retrievewhatsappmessagestatus.md): Retrieves the delivery status of a specific WhatsApp message by its message ID. Returns the current status, conversation details, and any error information if the message failed to deliver.
