Skip to main content
Solved

Generating Access Token with HTTPCaller

  • September 13, 2024
  • 3 replies
  • 69 views

jonvelco
Contributor
Forum|alt.badge.img+3

I’m following this API documentation to authenticate and can successfully do so in Postman.  However, with the HTTPCaller it keeps returning a 400 error:

    "error": {
        "code": "no_grant_type_provided",
        "message": "Bad Request",
        "status": 400
    },

I feel like I’m close but can’t crack this nut...what am I doing wrong??

 

Postman:

Postman

 

HTTPCaller:

HTTPCaller

 

Best answer by nielsgerrits

Not sure if this causes any issues, but the way you do send the Content-Type header is duplicate. You can either use the header row or the Content Type field. What happens if you leave the Content Type field empty?

Did you validated the json using something like NotePad++?

View original
Did this help you find an answer to your question?

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+54
  • Best Answer
  • September 13, 2024

Not sure if this causes any issues, but the way you do send the Content-Type header is duplicate. You can either use the header row or the Content Type field. What happens if you leave the Content Type field empty?

Did you validated the json using something like NotePad++?


jonvelco
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • September 13, 2024

Bingo - I removed the “Content-Type” header and tried again and low and behold it worked...thank you!  I’ll start gluing my hair back on now….


nielsgerrits
VIP
Forum|alt.badge.img+54
jonvelco wrote:

Bingo - I removed the “Content-Type” header and tried again and low and behold it worked...thank you!  I’ll start gluing my hair back on now….

:) this stuff can be a bit frustrating yes, but happy it works now :)

Another important tool is PostMan Echo, where you can send requests to so you are able to see what you actually are sending.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings