Workfront API in AWS Glue Job Returns HTML "Invalid Access Token" Instead of JSON and shows Json Decode Error. | Community
Skip to main content
Y
Yetheshwar
August 14, 2025
Question

Workfront API in AWS Glue Job Returns HTML "Invalid Access Token" Instead of JSON and shows Json Decode Error.

  • August 14, 2025
  • 2 replies
  • 264 views

I’ve been retrieving data from Workfront using both API key and Basic Auth. It works fine when I run the script locally, but when I run it inside an AWS Glue job, I get a JSONDecodeError.

 

On checking the response, it’s actually HTML with the message "Invalid access token" — even though the credentials are correct.

 

Has anyone faced this before? Could this be related to Glue’s environment, authentication method, or network configuration? Any guidance would be appreciated.

2 replies

Kurt_Jones
Community Advisor
Kurt_JonesCommunity Advisor
Community Advisor
August 20, 2025

Yetheshwar,

You've already answered your own query.  You had success using the Workfront API with its most common auth methods of API key an and Auth authentication.  I don't know AWS Glue or anything about it but it is likely infusing something it wants from the payload that WF has no idea what to do.  Sorry I couldn't be more helpful.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 1, 2025

    @yetheshwar just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...