endpoint: /api/v2/ticket.json and /api/v2/ticket_audit.json
response:
{"error":"Forbidden","description":"You are missing the following required scopes: read"}"

• Eric Nelson

  • 2022년 03월 30일 13:43

  Zendesk Developer Advocacy

  Hey Mike,
  
  Are you wrapping the scopes in an array? If not I'd try that "scopes": ["tickets:read", "users:read", "auditlogs:read"].
  
  Let me know if this doesn't fix your issue!
  
• Mike Chiu

  • 2022년 04월 11일 07:24

  Hi Eric, thanks for your reply.

  the setting with array does not work either.

  But after I re-testing again with scope: "tickets:read users:read auditlogs:read" both in authorization and token retrieval API, it works now.

  BTW, when I use `scopes: ["tickets:read", "users:read", "auditlogs:read"]` as parameters for authorization and token retrieval, the consent page displayed without any scopes shown. Then I can get access_token successfully, but failed to get user profile with 403 forbidden error.

  thanks for your help, I think I will use the space delimited string as scope while applying authorization.

• Mike Chiu

  • 2022년 04월 22일 03:29

  Hi Eric, 

  The scopes for access token retrieval works now.

  But there's an issue for `ticket_audits` retrieval.

  When I use "tickets:read auditlogs:read users:read" as my requested scopes and get access token successfully, I can use this token to get tickets, list tickets via get endpoint.

  But for ticket_audits endpoint, the response is 403 with response:

  {
    "error": "Forbidden",
    "description": "You are missing the following required scopes: read"
  }

  And from all document mentioned with scope, none of them bring up scope about ticket_audits.

  Can you help check if there's an issue for this scope ? Thanks.

• Greg Katechis

  • 2022년 04월 22일 20:18

  Zendesk Developer Advocacy

  Hi again Mike! A colleague and I just did some testing and it turns out the ticket audits endpoint requires global read scoping in your token. My guess is that it's because ticket_audits can contain additional data that isn't being explicitly scoped in the token. I'll send a request along to one of the two teams that would be required to make a decision on adding additional scopes to try and get that added. I'll let you know when I hear back from them if that's something that will be possible down the line.
   
  Let me know if you have an additional questions!
  
• Mike Chiu

  • 2022년 04월 23일 04:03

  Hi Greg Katechis,

  Thanks for you reply, on my testing, there is no specific scope for incremental export API either.

  it would be appreciated if you can send Incremental Export API scope to discuss as well. 

  Thanks!

• Viktor Novistskyi

  • 2023년 06월 07일 12:07

  Hi Greg Katechis

  I have a similar issue when trying to 

  • GET /api/v2/ticket_fields

  error is 

  {
    "error": "Forbidden",
    "description": "You are missing the following required scopes: read"
  }

  For getting the Oauth access token I use a code approach with scope tickets:read.

  I can get the tickets list, but other request fails. What scope should I use for getting ticket_fields?

• Greg Katechis

  • 2023년 06월 07일 18:16

  Zendesk Developer Advocacy

  Hi Viktor! After doing some investigation on my end, it looks like access to the ticket_fields API requires global read access. I can look into this as a possible feature request for the future, for the time being it appears that you will need the global read access for now. 

• Kirsten

  • 2023년 09월 06일 16:47

  Hi, can anyone confirm whether or not the `tickets:read` scope will work for making GET requests to the incremental exports API? (/api/v2/incremental/tickets) I've searched for this in documentation but haven't found anything. Thanks!

• Christopher Kennedy

  • 2023년 09월 14일 16:31

  Zendesk Developer Advocacy

  Hi Kirsten,
   
  Incremental export API requests also require global read access.
  

댓글을 남기려면 로그인하세요.