Skip to main content
Answered

Include activeContentId in Articles API Response, to create direct links to help articles


Hi Intercom,

We're building tools to help our team manage help center content more efficiently, but we've encountered a discrepancy that's causing some challenges.

Currently, the article ID returned through the Articles API (/articles endpoint) doesn't include the activeContentId required in the Intercom app URL for editing articles. For example:

This means we can't programmatically generate direct links to the article editor in the Intercom app using the data from the API response.

Request: Could you consider adding the activeContentId to the API response? This would allow us to generate accurate deep links to articles in the Intercom app editor, making it much easier for our team to quickly access and edit specific articles.

Current API response:

{ "id": "10515400", "type": "article", "workspace_id": "ej501111", ... }

Proposed addition:

{ "id": "10515400", "active_content_id": "11181100", // New field "type": "article", "workspace_id": "ej501111", ... }

This would help teams like ours create more efficient workflows for content management within Intercom.

Thanks,

Simon

Best answer by Diogo Silva

Hi Simon, nice to meet you :) Unfortunately the Intercom API does not include this field in the response. The API returns basic article information such as id, type, workspace_id, title, and URL. I agree with you, although I believe that Intercom cannot make immediate changes, but they listen to the community a lot so it is important that we continue to move forward here. For now, you may need to explore alternative methods to generate your direct links, if a future update brings these improvements I will come back here to let you know 😀

View original
Did this topic help you find an answer to your question?

2 replies

Diogo Silva
Forum|alt.badge.img+1
  • Active User
  • 23 replies
  • Answer
  • February 11, 2025

Hi Simon, nice to meet you :) Unfortunately the Intercom API does not include this field in the response. The API returns basic article information such as id, type, workspace_id, title, and URL. I agree with you, although I believe that Intercom cannot make immediate changes, but they listen to the community a lot so it is important that we continue to move forward here. For now, you may need to explore alternative methods to generate your direct links, if a future update brings these improvements I will come back here to let you know 😀


  • Author
  • New Participant
  • 1 reply
  • February 11, 2025

@Diogo Silva totally understand. My post is to flag it as an issue and I’m sure someday it will get fixed. 

For other people’s reference there is a workaround (valid as of today’s date). It requires copying some session tokens from your browser. But the following commands does work to extract the ContentID. You may need to work with the parameters to get everything you need.

curl 'https://app.intercom.com/ember/content_service/contents/search' \
  -H 'Accept: application/json, text/javascript, */*; q=0.01' \
  -H 'Content-Type: application/json; charset=UTF-8' \
  -H 'Cookie: intercom-session=<YOUR_INTERCOM_SESSION>; _intercom_session=<YOUR_INTERCOM_SESSION_ID>' \
  -H 'X-CSRF-Token: <YOUR_CSRF_TOKEN>' \
  -H 'X-Requested-With: XMLHttpRequest' \
  --data-raw '{
    "per_page": 100,
    "app_id": "<YOUR_APP_ID>",
    "content_wrapper_types": [8],
    "folder_filter_option": "none",
    "object_types": [120, 137, 129, 131, 134, 138],
    "sort_by": "title",
    "sort_direction": "asc",
    "add_highlight": false,
    "page_from": 0,
    "sort_by_content_type_first": 138
  }'

Regards, Simon


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings