Getting 403 error while accessing Zendesk WFM API endpoints. | Community
Skip to main content

Getting 403 error while accessing Zendesk WFM API endpoints.

  • June 29, 2025
  • 3 replies
  • 0 views
V

Hi team,

I followed the all the steps mentioned in the below documentation to generate the API token

https://support.zendesk.com/hc/en-us/articles/4408889192858-Managing-API-token-access-to-the-Zendesk-API

 

However, when I call the endpoint below
curl --location 'https://{subDomian}.zendesk.com/wfm/public/api/v1/activities?startTime=1722105600' \
--header 'Authorization: Basic XXXXX' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json'
I receive a 403 error with the message "JWT not found."
Could you please help us understand the reason for this error and how to resolve it?

 

 

    3 replies

    Greg29
    • Greg29
    • June 30, 2025

    Hi Vinod,

     

    It does not look like you're passing the API token in correctly. Take a look at the documentation here for information on how to do this.

    V
    • Vinod11
    • Author
    • July 1, 2025

    Hi Greg,
    I am passing the API token correctly. When I call the users.json endpoint, I receive a 200 response, but when I call the endpoint below, I am getting 500 error as shown in below figure.
    curl --location 'https://{subDomian}.zendesk.com/wfm/public/api/v1/activities?startTime=1722105600' \
    --header 'Authorization: Basic XXXXX' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json'

    Could you please look into this and let me know if I'm missing something?
     

    Greg29
    • Greg29
    • July 1, 2025

    Hi Vinod,

     

    So it sounds like the original 403 is no longer an issue and now you're getting a 500 response? This would be indicative of a different problem not related to your auth and requires some account-level troubleshooting that we wouldn't want to do in a public forum. Could you reach out to our Advocacy team following the instructions in this article so that we can look further into that for you?

    Terms & ConditionsCookie settingsAccessibility statement