Support for x-www-form-urlencoded headers

I’m trying to connect to a REST API that requires x-www-form-urlencoded in the content-type header. According to https://learn.parabola.io/docs/troubleshooting-connecting-to-an-api, this isn’t currently supported by Parabola. Would it be possible to add support for this type of API? Right now, I have to use Postman to generate a the bearer token that is used by the API to authorize subsequent requests. That’s making it impossible for me to fully automate a flow.

Hi Michael! I went ahead and moved your post into our Feature Request category. I can definitely understand why you’d want this to be supported to be able to fully automate your flow.

Out of curiosity, what API are you using?

Hi Sachi,

Thanks for the quick response. The API I need to connect with is for the iMIS member management system. Only the initial request to get a token requires that header:

https://developer.imis.com/v1.0.1/reference/bearer-token

All subsequent requests have the content-type header as application/json.

-Michael

Thanks for the additional info! We’ll continue monitoring this request for the time being.