[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fATUBmhyya_mwAROF2lUSHmSUqe3wWADdgH2w8KwH0-Y":3,"$fIV6Oo8iFvmW1j6rdVglKkCA90dqdR28n0a-C0OPOXUA":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"intercom-openapi","Intercom REST API","intercom","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fintercom\u002FIntercom-OpenAPI\u002Fmain\u002Fdescriptions\u002F2.15\u002Fapi.intercom.io.yaml",{"id":13,"contentHash":14,"fetchedAt":15},"01KWHWCXPXEJHG534S8Y5W5W12","a501eb962569dbe5a47c63597a29c19faf9a9188eba7252e61be942648ee9ed9","2026-07-02T17:00:36.371Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX38JY9Q0A2XN58D5A79JTSK","a2fc2aa191aa2fab97ffd8e78201faf7149525ad80639c69b8acb1c80e6ba03c","2026-07-09T11:00:41.718Z",null,{"alerts":22},[23,30,37,44,52,59,66,73,80,87,94,101,108,115,122,129],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX38K7GFV2VZFA6669THTDN2","Breaking","merge_contacts_request fields 'from' and 'into' are now required","The `merge_contacts_request` schema now marks **`from`** and **`into`** as `required` fields. Clients that previously omitted either field (relying on them being optional) will now fail schema validation. This affects any integration that merges contacts without explicitly providing both identifiers.","2026-07-09T11:00:51.855Z","2026-07-09-merge-contacts-request-fields-from-and-into-are-now-required",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KWHWD10AK8A2GZAZTZ2FSNSP","Informational","Clarify timestamp field search behavior across timezones","Documentation updated to clarify that Contact Search timestamp field queries are interpreted using the workspace's timezone rather than UTC, which can cause different results across workspaces. This is informational documentation explaining existing behavior, not a functional API change.","2026-07-02T17:00:40.330Z","2026-07-02-clarify-timestamp-field-search-behavior-across-timezones",{"id":38,"severity":32,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KWEZPW0QYC3BR4F7RRMTR3ZQ","Reorganize export API under new \"Reporting Data Export\" tag","The OpenAPI specification reorganized four export-related endpoints under a new **Reporting Data Export** tag (replacing the generic **Export** tag). A new tag definition was also added with documentation and a help article link. This is purely a documentation\u002Forganizational change with no impact on API behavior or functionality.","d87b1f60ff04490107d7fc5920bc80ecd677247d5599f201037e4900ad566bd8","2026-07-01T14:00:45.335Z","2026-07-01-reorganize-export-api-under-new-reporting-data-export-tag",{"id":45,"severity":46,"title":47,"summary":48,"contentHash":49,"detectedAt":50,"slug":51},"01KW9GMT5FTYD9QGAEBC8X4V4Q","Additive","Away status reasons endpoint now returns structured list","The GET request to retrieve away status reasons now returns a wrapped response object with `type` and `data` fields instead of a raw array. A new `away_status_reason_list` schema was introduced to structure the response as `{type: \"list\", data: [array of away_status_reason objects]}`. This change ensures consistency with other Intercom list endpoints and properly encapsulates the list metadata.","ba6f5a720ae9f7bce6c061b06e8fb0bd507fca4edfad4fa3ebe718899119108b","2026-06-29T11:01:17.103Z","2026-06-29-away-status-reasons-endpoint-now-returns-structured-list",{"id":53,"severity":46,"title":54,"summary":55,"contentHash":56,"detectedAt":57,"slug":58},"01KVZR6PTHH73KHVPP3TRBHTPG","Add audience_ids support to content import sources","The Intercom API adds optional `audience_ids` field to content import source objects and a new optional `apply_audience_to_existing_content` parameter for updates. These are purely additive changes — the new fields are optional and nullable, so existing clients will continue to work without modification. The changes enable customers to associate and manage audiences with content import sources.","a8b5c27b93766e7ee8de8bfd0f64614309b673a1b2529b7a1671fc5749793d12","2026-06-25T16:00:59.217Z","2026-06-25-add-audience-ids-support-to-content-import-sources",{"id":60,"severity":32,"title":61,"summary":62,"contentHash":63,"detectedAt":64,"slug":65},"01KVWVFPJMFJN3616EZE6ZZV7E","Clarified subscription endpoint response behavior","Added clarification to the subscriptions endpoint documentation explaining that it only returns subscriptions where the contact has explicitly configured their preference, and excludes subscriptions in default state. This is documentation-only and does not change the actual API behavior.","4e0b37e6856a388b941015c7452537997f7a55a0e09709ef2591f62f9a0ea9e8","2026-06-24T13:00:36.308Z","2026-06-24-clarified-subscription-endpoint-response-behavior",{"id":67,"severity":32,"title":68,"summary":69,"contentHash":70,"detectedAt":71,"slug":72},"01KVTKCNS31P04V6ANBQD9NWK6","Clarify date range constraints on message event timestamps","Updated descriptions for 11 message event timestamp fields to clarify that only events within the export job's requested date range are counted. This is a documentation clarification that does not change the API's behavior or contract—it explains existing behavior more clearly to help customers understand timestamp filtering in export operations.","2f507c9e987cd435502309e0eb6360b3206cca93f2607dfaaacda8d04dae029a","2026-06-23T16:00:39.715Z","2026-06-23-clarify-date-range-constraints-on-message-event-timestamps",{"id":74,"severity":46,"title":75,"summary":76,"contentHash":77,"detectedAt":78,"slug":79},"01KVR0ZWVMWD2GRP5950F0R2VQ","Add GET \u002Fconversations\u002F{id}\u002Fhandling_events endpoint","New endpoint `GET \u002Fconversations\u002F{id}\u002Fhandling_events` added to list pause\u002Fresume events for conversations, along with supporting schema definitions (`handling_event`, `handling_event_list`, and `teammate_reference`). This is a purely additive change that cannot break existing integrations.","06004d58656fd4516de8f52e12fc23fed9e7c11c09a0fe0202b9cb8a7559e306","2026-06-22T16:00:37.748Z","2026-06-22-add-get-conversations-id-handling-events-endpoint",{"id":81,"severity":32,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KVB509BYAHD6YMX9TWS265G2","Documentation update: bot email reply behavior clarification","The `POST \u002Fconversations\u002F{id}\u002Freply` endpoint description now includes a warning admonition explaining that bot or Operator replies to inbound email conversations are not sent to customers by default—they're stored as unnotifiable bot comments. This is a documentation clarification with no changes to API behaviour, parameters, or response structure.","d732e3d32ce982c8875d37b0f43c7510cd2eafe98d1ef9595d7b8e601b890ba2","2026-06-17T16:00:37.246Z","2026-06-17-documentation-update-bot-email-reply-behavior-clarification",{"id":88,"severity":46,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KV5F1K83M6BWG85HDW1RGJX2","Allow boolean values in custom attribute schema","The custom attribute `value` field schema now accepts `boolean` type in addition to the existing string, integer, and array types. This is purely additive—existing integrations continue to work, and clients can now optionally send boolean values for custom attributes.","8c9d3c22ec519c585e394569e8a016876464da3aa608367def4c6eda3b40cf4b","2026-06-15T11:00:39.299Z","2026-06-15-allow-boolean-values-in-custom-attribute-schema",{"id":95,"severity":46,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KT4H1M5AKQKHB0C6A2T401KC","Support for Intercom API v2.15","The `intercom_version` parameter now includes `2.15` as a valid enum value, with the default version updated from `2.14` to `2.15`. This is purely additive — existing integrations using earlier versions will continue to work.","e178b66cd2e9ccb5258e1a287d6b9cf786dda364356889dfdbdcb81460ab8dce","2026-06-02T16:00:41.130Z","2026-06-02-support-for-intercom-api-v2-15",{"id":102,"severity":25,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KSSJWJ3PRNQBNK84XYM0ZSVN","PUT \u002Fconversations\u002F{id} now returns 400 on duplicate custom attribute names","The `PUT \u002Fconversations\u002F{id}` endpoint now returns a `400 INVALID_PARAMETER` error when the request body includes `custom_attributes` and the workspace has multiple non-archived conversation custom attributes sharing the same name. Previously, the request would silently succeed by applying the update to a non-deterministic attribute. Clients that rely on the old silent-success behaviour will now receive an error and must resolve duplicate attribute names in workspace settings before retrying.","5530e1ca83ce63fd8f7a291e4624fb96df2a68f9f3ff6d9693a67bad069e0d78","2026-05-29T10:01:13.590Z","2026-05-29-put-conversations-id-now-returns-400-on-duplicate-custom",{"id":109,"severity":32,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KSQRGMB3T0XTGA6ZD2KWR5AF","Clarify timestamp format in contact field descriptions","Updated documentation for multiple timestamp fields on contact objects to explicitly state they are Unix timestamps in seconds (rather than just \"UNIX timestamp\"). This clarification helps developers understand the exact time unit for fields like `created_at`, `updated_at`, `signed_up_at`, and several others, but does not change the actual API behavior or response format.","7900f63d3f98b031e15b9d09edb4e0c719f5979598022b3097263b65abc1714e","2026-05-28T17:01:05.251Z","2026-05-28-clarify-timestamp-format-in-contact-field-descriptions",{"id":116,"severity":32,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KSMVSPHH6GK90T7BW1ES66YT","Clarified detachContactFromConversation operation docs","Updated the description and warning section for the `detachContactFromConversation` operation to clarify that it removes (rather than adds) contacts from group conversations and cannot remove the last participant. This is a documentation correction that does not change the API's actual behaviour—it makes the docs more accurate.","84f70f9948a624fb1d250aa2e10ffc3b90d762ac0f00953040d667a6a8d5a4f3","2026-05-27T14:00:44.849Z","2026-05-27-clarified-detachcontactfromconversation-operation-docs",{"id":123,"severity":46,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KSJG90ZQ0QK6DHV86V8CY8WQ","Add ai_sales_agent_availability response field","The response schema now includes a new optional `ai_sales_agent_availability` boolean field that indicates whether an external page can be used to answer questions by AI Sales Agent. This is a purely additive change that does not break existing integrations.","a984072a2520e6da658c116c48b3b0325bebd565c09d5a7f1cb5e7172bce079a","2026-05-26T16:00:55.287Z","2026-05-26-add-ai-sales-agent-availability-response-field",{"id":130,"severity":46,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KS35A96H3KE4A31YHQK8K1BV","Add hide_csat_from_agents_setting_change activity type","A new enum value `hide_csat_from_agents_setting_change` has been added to the activity type list in the Intercom REST API. This is a purely additive change that allows clients to handle a new workspace setting activity type without breaking existing integrations.","fa8ae6954135d52816f206a5eb4ff0ac69ae113049f09ccc6c40a009c428e1d2","2026-05-20T17:00:45.649Z","2026-05-20-add-hide-csat-from-agents-setting-change-activity-type"]