Assistance Required – HTTP Call (Basic Auth) Error in Workato

[Aiswarya]

Hi Team,

I am new to the Workato platform and currently working on an HTTP call using Basic Authentication. I tested the same request in Postman, and it worked fine. However, when I try to make the call in Workato, I’m encountering errors.

• When I include the username and password in the connection, I receive a 400 error:
  “The server cannot or will not process the request due to a client error (for example, incorrect syntax or missing headers).”

• When I include the credentials as a header, I receive a 401 Authorization error.

Could you please help me identify what might be causing this issue and how to properly configure the connection in Workato?

Thank you for your support. 

[shivakumara]

Hi @Aiswarya ,
In Postman, you have used Basic Authorization to configure by passing the username and password.

In Workato, the recommended approach is to configure authorization at the connection level rather than sending credentials in headers for every request. This ensures:

• Security: Sensitive information is not repeatedly exposed in request headers.
• Maintainability: Credentials are managed centrally, making updates easier.
• Compliance: Reduces risk of accidental leaks in logs or shared recipes.

Thanks and Regards,
Shivakumara K A

[Aiswarya]

Hi Shivakumara,
Thank you so much for your response — I really appreciate your support.
As mentioned in my earlier message, I tried the case you specified, but it’s returning a 400 error:

“The server cannot or will not process the request due to a client error (for example, incorrect syntax or missing headers).”

Could you please assist me in resolving this issue? I’d like to understand whether it’s necessary to include specific data in the header, or what exactly might be causing this error.

Thank you again for your help!

[rajeshjanapati]

Hi @Aiswarya,

The reason why it is worked in POSTMAN is, as it by default encode the username and password to base64. For reference you can also check in code (</>) section with python requests where your username and password is encoded.

so, as @shivakumara mentioned you have provided the credentials in the connection page and connections got successful right??

If connection got successful then no need to provide username and password in HTTP configuration or guided set-up page, directly proceed with parameters. If you face any errors please share the screenshots.

Thanks & Regards,

J Rajesh Kumar.

[shivakumara]

Hi @Aiswarya ,
From the screenshots provided, it appears that Basic Authentication details were not configured at the connection level, and instead, everything is being set up within the recipe.

I recommend adding the username and password in the connection settings and then establishing the integration.
If you need further assistance after that, please let us know.

Providing authorization details in recipes is not advisable when the option exists to configure them at the connection level.

Here I am adding your screenshot where you haven't provided credentials in connection.

Thanks and Regards,
Shivakumara K A