• Tipene Hughes

  • 5 de maio de 2022 18:35

  Zendesk Developer Advocacy

  Hey, Adam!
   
  A 403 response would indicate that the account does not have the required permissions to alter the article in question. I'd suggest having your client have a read through this article to ensure their permissions have been set correctly, and trying the API request again once the necessary changes have been made.
   
  Understanding Guide user permissions for knowledge base access
   
  I hope this helps! Feel free to reach out if you run in to any further issues.
   
  Tipene
  
• Adam Jelewski

  • 6 de maio de 2022 09:04

  Hi Tipene,

  Thank you for the feedback I will forward your response to the client.

  However, can you please help me to understand why the response body is empty in this case?

  Some time ago I was using the same API Calls as troubleshooting steps to investigate a similar issue for another client of ours. The response was also 403 but the body returned was:

  {
      "error": {
          "title": "Forbidden",
          "message": "You do not have access to this page. Please contact the account owner of this help desk for further help."
      }
  }

  But once again I see no response now.

   

  Thanks,

  Adam

• Tipene Hughes

  • 6 de maio de 2022 13:41

  Zendesk Developer Advocacy

  Hey Adam,
   
  I agree that it is frustrating to not have a descriptive message returned in the response body. I'll pass this on to the team that owns this API to look in to having the response updated with more context in the case of a 403 error.
   
  Thanks!
   
  Tipene
  
• Adam Jelewski

  • 6 de maio de 2022 14:51

  Hell Tipene,

  Thank you for the continued support, our client states that he can access the article in question as well as edit it. The account has no restrictions to any of the tickets.

  I am looking forward to the additional information.

   

  Thanks,

  Adam

• Tipene Hughes

  • 9 de maio de 2022 18:40

  Zendesk Developer Advocacy

  Hi Adam,
   
  That's strange. I'm going to pull this in to ticket so we can take a look in a bit more detail. You should see an email come through from the shortly!
  
• Dev account

  • 21 de junho de 2022 13:45

  Hello Adam,
  
  

  What brand are you trying to use? I face the same issue with 403 and 401 with Guide API for the non-main brand(where the instance subdomain isn't the same as the help centre subdomain).

  For example, if your app is on https://instance.zendesk.com, then API calls with be ok for https://instance.zendesk.com/api/v2/help_center and fail for https://instance-uk.zendesk.comapi/v2/help_center(some of them are still ok).
  
  I also need a solution here, because it seems like a Guide API bug and we can't do much. I was able to fix this issue via oAuth tokens, but only for admin users.
  
  Thanks,
  Andriy

• Tipene Hughes

  • 6 de julho de 2022 17:19

  Zendesk Developer Advocacy

  Hey Dev account,

  Thanks for reaching out!

  Are you still experiencing the issue you mentioned above? If so, one area I'd suggest checking first is content blocks. There are certain scenarios that will cause you to receive a 403 when content blocks have been enabled in your help center. This article goes in to more detail:
  
  https://developer.zendesk.com/documentation/help_center/help-center-api/using-the-help-center-api/content-blocks-limitations/

  If you continue to run in to issues, please let me know and we can look in to it in more detail.

  Thanks!

  Tipene

• Dev account

  • 18 de julho de 2022 08:17

  Hello Tipene, 
  
  Sorry for the long reply, and thanks for your advice. There is no issue with content blocks because they were disabled in my instance. I think the problem with Guide API when requesting from the Zendesk app. In this case, we can't use API tokens to authenticate requests, so Guide API fails for brands with different URLs.
  Any help will be appreciated because I can't prepare the app for the marketplace because of this problem.
  
  Thanks, 
  Andriy

   

• Christopher Kennedy

  • 26 de julho de 2022 11:52

  Zendesk Developer Advocacy

  Hi Andriy,
   
  This is actually expected behavior because we only implement CORS for API requests authenticated via OAuth.  As an alternative, you may create a server-side app that runs in the app iframe.  This would allow you to successfully send requests to multiple domains.
  
• Dev account

  • 26 de julho de 2022 12:13

  Hello Christopher,

  Thanks a lot for the explanation. I'll consider a server-side option for this app. 

  Best regards,
  Andriy

Por favor, entrar para comentar.