About the API Changelogs
Below you can find links to changelogs that detail changes to the API from each version. You can also see our definition of a breaking change.
To access new features, you'll need to change your API version in the Developer Hub or set a version in the header of your API call.
Changelogs
| Changelog | Release date | Docs |
|---|---|---|
| Unversioned changes | Ongoing | Reference |
| Unstable | Ongoing | Reference |
| 2.11 | 2024-05-03 | Reference |
| 2.10 | 2023-09-14 | Reference |
| 2.9 | 2023-01-24 | Reference |
| 2.8 | 2023-01-24 | Reference |
| 2.7 | 2022-12-07 | Reference |
| 2.6 | 2022-10-18 | Reference |
| 2.5 | 2022-06-07 | Reference |
| 2.4 | 2021-12-13 | Reference |
| 2.3 | 2020-11-12 | Reference |
| 2.2 | 2020-08-12 | Reference |
| 2.1 | 2020-07-14 | Reference |
| 2.0 | 2020-01-30 | Reference |
| 1.4 | 2019-09-26 | Reference |
| 1.3 | 2019-06-05 | Reference |
| 1.2 | 2019-05-03 | Reference |
| 1.1 | 2018-10-16 | Reference |
| 1.0 | 2018-10-15 | Reference |
About breaking changes in the Intercom API
The Intercom API is a versioned API. The version number increments by 0.1 each release, unless we introduce major new functionality, in which case we will increment by 1. We do not follow Semantic Versioning.
Any breaking changes will be released in a new API version. Breaking changes are changes that can potentially break an integration. Breaking changes can include:
- removing an entire operation
- removing or renaming a parameter
- removing or renaming a response field
- adding a new required parameter
- making a previously optional parameter required
- changing the type of a parameter or response field
- removing enum values
- adding a new validation rule to an existing parameter
- changing authentication or authorization requirements