New 42-day free trial Get it now

RecommendedSmarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocodingJanuary 27, 2026 USPS Web Tools rate limit capped at 60 requests per hour: How to prepare and why many are choosing SmartyDecember 3, 2025 Pinpoint 2025: Day 1 recapNovember 28, 2025

SECURITY ANNOUNCEMENT: Removing old TLS versions

Smarty header pin graphic

Jonathan Oliver

Jonathan Oliver

Updated October 29, 2025

Tags

Technical support

Smarty header pin graphic

TLS (and its predecessor SSL) are cryptographic protocols that provide authentication and data encryption for clients connecting with web servers. As new vulnerabilities are discovered, older cryptographic protocol versions are deprecated to maintain secure environments.

On Tuesday, January 21, 2020, Smarty will require clients to use TLSv1.2 or greater to connect with Smarty APIs without interruption. Clients using TLSv1.0 or TLSv1.1 will no longer be able to connect. Please refer to our documentation for more information: https://www.smarty.com/docs/cloud/requirements#ciphers

To see if your client software is able to properly connect, please use our test page: https://test-tls.api.smarty.com/

The industry, in general, is removing support for older TLS versions. Please refer to the following announcements from major browser vendors for more information:

https://blog.mozilla.org/security/2018/10/15/removing-old-versions-of-tls/
https://webkit.org/blog/8462/deprecation-of-legacy-tls-1-0-and-1-1-versions/
https://blogs.windows.com/msedgedev/2018/10/15/modernizing-tls-edge-ie11/
https://security.googleblog.com/2018/10/modernizing-transport-security.html

Subscribe to our blog!

Learn more about RSS feeds here.

Read our recent posts

Verification update: Add provisional addresses to Smarty’s database

With the launch of our latest product feature, US Provisional Address Manual Process, US Address Verification users can now submit new or missing addresses, and we’ll verify them against authoritative databases and add any approved records to our database. Better yet, you won’t need to make any integration changes to see your addresses in your API results, it won’t take longer than 30–60 days, and it won’t cost you anything extra. That’s what we call an all-around win!Let us take the stress of verifying new or missing addresses off your plate so you can focus on what you do best.

Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly

SDK authors live in a permanent tug-of-war:Users want a simple constructor they can paste and ship. Maintainers want room to grow without breaking everybody’s build on the next release. That second part matters a lot right now, because a lot of people are still relatively early in their software careers. Approximately one in three developers has coded professionally for four years or less. That matters because unclear or fragile APIs disproportionately hurt newer developers—they don’t have scars yet.

Ambiguous address matches: What they are and why compliance teams should care

If you’ve ever run into an address that seems to exist in more than one place, congratulations—you’ve discovered the world of ambiguous address matches. They’re the Schrödinger’s cat of location data: valid, yet potentially two distinct locations. This blog will focus on a few key things: What are ambiguous address matches?Why ambiguous address matches matter for compliance and customer serviceHow to handle matches with address ambiguityWhy you should inform your customers of ambiguous address matchesOur final thoughts on ambiguous address matchesWhat are ambiguous address matches?An ambiguous address match occurs when an entered address resolves to two or more valid locations with slight but meaningful differences.

Ready to get started?