Expect Non-HTTPS Freshsales API Requests to respond with 302 (starting July 15)

What is the change?

In order to strengthen security, Freshsales :freshsales: will begin to redirect all Non-HTTPS requests made to the product with a 302 response starting July 15.

How are developers likely to be impacted?

Freshsales Developers who might be making non-HTTPS calls to the product using a client that does not handle the 302 redirect will start to see their API requests fail.

What can I do if I am impacted?

Update your clients to simply use HTTPS API endpoints when making API calls to :freshsales:. If you run into any trouble, reach out to us here on the community!