Good, but make sure you understand that this is not a safe method.
See https://winscp.net/eng/docs/faq_hostkey#obtaining

Thank you for the reply Martin. I was able to find the new host key fingerprint by connecting manually and going to Session -> Server / Protocol Information and copying the value for SHA-256.
https://winscp.net/eng/docs/ui_fsinfo

As the message says, the your server's hostkey does not match anymore the fingerprint in your commandline.
Either your server got hacked. Or (more likely) it got reconfigured/reinstalled and the host key has been changed as part of that. Talk to your server administrator to verify this. If the change was legitimate, update the fingerprint in the commandline.

I have an automated script that calls WinSCP from the command line and feeds in the hostname and credentials. This worked up until recently. I'm now getting an error that 'Host Key does not match key fingerprint'. I confirmed that I'm able to manually connect to the SFTP site (log attached). Here is the command I send to automate the request:

This is SAS -> calling command prompt -> calling WinSCP