Home//
REST API Reference
/- List article versions
List all articles
Create an article
Retrieve an article
Update an article
Delete an article
Retrieve an article draft
Stage an article draft
Publish an article draft
Add a tag to an article
Remove a tag from an article
Retrieve an article version
Search for articles
Article
Articles
Article Search Highlights
Article Search Response
Article Version
Article Version Summary
Internal Article
List article versions
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 GET /articles/{article_id}/versions/{id} to retrieve a single version with its full content.
Requires the read_articles_scope OAuth scope.
Security
bearerAuth
Intercom-Versionstring(intercom_version)
Intercom API version.
By default, it's equal to the version set in the app package.
Default:"2.16"
Enum:"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"
Example:2.16
- The production API serverhttps://api.intercom.io/articles/{article_id}/versions
- The european API serverhttps://api.eu.intercom.io/articles/{article_id}/versions
- The australian API serverhttps://api.au.intercom.io/articles/{article_id}/versions
curl -i -X GET \
'https://api.intercom.io/articles/123/versions?page=1&per_page=25&locale=en' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Intercom-Version: 2.16'Versions found
pagesobject or null(Cursor based pages)
Cursor-based pagination is a technique used in the Intercom API to navigate through large amounts of data. A "cursor" or pointer is used to keep track of the current position in the result set, allowing the API to return the data in small chunks or "pages" as needed.
dataArray of objects(Article Version Summary)
An array of Article version summary objects.
Response
{ "type": "list", "pages": { "type": "pages", "page": 1, "per_page": 25, "total_pages": 1 }, "total_count": 2, "data": [ { … }, { … } ] }