Article Owner API endpoint

Hi @dinesh11, 

Thank you for sharing your case. We don't have any immediate plans to change our current API. But I'll make sure to note down this request for the future. 

I agree with this feedback post. Currently, this field is not reportable in Explore. Furthermore, we cannot get this data from the Help Center API. Since we use the Owner field as the individual who is responsible for maintaining the article, this is the field that is most up to date, not the author field. The author field is the first person that created the article. Thus, we need a way to be able to export and report on the Owner field, but we currently do not have one.

We need this too. Really frustrating that you can't use the API to create a list of article owners (or those that are missing ownership) or to be able to automatically assign a ticket (when being created) to the group of the article owner (when clicking through via the article to create a new ticket)

This is a big dropped ball here - disappointing that this basic functionality was not included in the API.

I would also appreciate it if the API included the functionality to retrieve the Article Owner please.

In order to safeguard our Articles, we have followed the instructions provided at: https://developer.zendesk.com/documentation/help_center/help-center-api/using-the-help-center-api/backing-up-your-knowledge-base-with-the-help-center-api/

Within the user interface, we have begun utilising the Article Owner feature to differentiate the team associated with each article. However, since the Article Owner is not available in the API, we are unable to back up articles against their respective owners. Consequently, we will face challenges when attempting to restore Articles for specific Owner Groups.

Posting an update here, we've managed to get it working (unpublished/unsupported method, but is working for now):

GET https://yourcomain.zendesk.com/knowledge/api/articles/articleid

The JSON response includes this block:

  "owner": {

This Article Owner API endpoint is very import for me. Now we are using ('/guide/graphql') to get the owner, but in earlier, we were asked to update the API to v2, the old API will be discontinued by 30th of this month. I searched the documentation and asked tech support, and the result is that we don't have an API to get the ‘Owner’ we want, and that there are properties ‘Template’ and ‘review statuses’ in the same case.

Are there any plans to update the API to allow us to get the Article “Owner”?

@ian12 Try this:

curl -X POST "https://yoursubdomain.zendesk.com/api/graphql" \
 -H "Content-Type: application/json" \
 -H "Authorization: Bearer YOUR_TOKEN" \
 -H "apollographql-client-name: GuideClient" \
 -H "apollographql-client-version: 0.0.1" \
 -d '{
   "operationName": "GetArticleOwner",
   "variables": {
     "articleId": "YOUR_ARTICLE_ID"
   },
   "query": "query GetArticleOwner($articleId: ID!) { article: guideArticleById(articleId: $articleId) { id owner { id type __typename } __typename } }"
 }'

Works for me, the response looks like:

{

"data": {

"article": {

"id": "ARTICLE_ID",

"owner": {

"id": "OWNER_ID",

"type": "GROUP",

"__typename": "GuideArticleOwner"

},

"__typename": "GuideArticle"

}

},

"extensions": {

"requestId": "9cbedbaecc6ca95c-SYD"

}

}


YMMV - Still not a ‘supported’ method.
 

GraphQL Example I got working (not sure why my earlier post didn't show up):

curl -X POST "https://yoursubdomain.zendesk.com/api/graphql" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "apollographql-client-name: GuideClient" \
  -H "apollographql-client-version: 0.0.1" \
  -d '{
    "operationName": "GetArticleOwner",
    "variables": {
      "articleId": "YOUR_ARTICLE_ID"
    },
    "query": "query GetArticleOwner($articleId: ID!) { article: guideArticleById(articleId: $articleId) { id owner { id type __typename } __typename } }"
  }'

Example Response:

{
    "data": {
        "article": {
            "id": "ARTICLE_ID",
            "owner": {
                "id": "OWNER_ID",
                "type": "GROUP",
                "__typename": "GuideArticleOwner"
            },
            "__typename": "GuideArticle"
        }
    },
    "extensions": {
        "requestId": "XXX"
    }
}

Note its still not an official/published API method/endpoint.