You can fetch the details of a single news item by making a GET request to http://api.intercom.io/news/news_items/<id>
.
Example Request & Response
curl --request GET \
--url http://api.intercom.io/news/news_items/65 \
--header 'accept: application/json' \
--header 'authorization: <Your access token>' \
--header 'content-type: application/json' \
{
"id": "24",
"type": "news-item",
"workspace_id": "tx2p130c",
"title": "Introducing Messenger-First Tickets!🎟",
"body": "<p>Hey there!</p>\n<p>Every customer need—from simple live chats to complex support tickets—can now start in the Messenger. 🌟</p>\n<p>The addition of tickets allows you to handle customer requests asynchronously. Chat agents can focus on replying to simple queries quickly, while other teams carry out escalations and operational tasks in the background using tickets.</p>\n<p>That means you can now resolve every customer issue entirely in Intercom.</p>\n<p><a href=\"https://www.intercom.com/help/en/articles/6436600-tickets-explained\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" class=\"intercom-content-link\">Read on.</a></p>",
"sender_id": 68,
"state": "live",
"labels": [
"Feature update",
"New feature",
"Product"
],
"cover_image_url": null,
"reactions": [
"💜",
"😴",
"👎",
"🎉"
],
"deliver_silently": false,
"created_at": 1668515591,
"updated_at": 1668515591,
"newsfeed_assignments": [
{
"newsfeed_id": 3,
"published_at": 1668515593
}
]
}
Request Path Parameters
Parameter | Type | Required? | Description |
---|---|---|---|
id | String | Yes | The unique identifier for the news item which is given by Intercom. |
Response
This will return a News Item model.