New 42-day free trial Get it now
Smarty

Address verification for fun and profit: Using Go SDK

Webinar recap address verification for fun and profit main image
Updated October 29, 2025
Tags
Webinar recap address verification for fun and profit main image

In our recent webinar, Ryan Cox, one of our highly skilled API developers, walked through setting up and using the Smarty Go SDK. The webinar covered various essential topics, from obtaining the SDK to understanding the ins and outs of implementation.

Ryan explained that the Smarty Go SDK is easily accessible on GitHub. He then moved on to discuss the key differences between embedded keys and secret keys. Embedded keys are ideal for client-side applications because they provide limited access and don’t reveal sensitive information. On the other hand, secret keys offer more extensive access and are suitable for server-side applications.

One of the highlights of the webinar was Ryan's demonstration on spot-checking your code. He emphasized the importance of ensuring the accuracy and efficiency of your code before integrating it into your system.

Next, Ryan discussed the wealth of information that can be obtained from the Smarty SDK. The SDK provides valuable address data, and could be used for things such as address verification, address autocomplete, and geocoding services. This sort of data allows businesses to improve operations and enhance customer experiences.

In addition to the Go SDK, Ryan mentioned other available SDKs, such as Python, Java, Ruby, and more. He encouraged attendees to explore the various SDKs to find the one that best suits their needs.

Want to watch Ryan get everything set up? You can view the recording in its entirety here.

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly
Arrow Icon
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
Arrow Icon
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.
Smarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocoding
Arrow Icon
OREM, UT, Jan 27, 2026—Smarty®, an expert in address data intelligence, today announced a three-part release designed to help organizations turn messy, fast-changing location data into operational confidence. The January 2026 bundle introduces: 1) A brand-new parcel dataset, 2) Expands provisional address programs into core U. S. products, and 3) Upgrades Smarty’s International Geocoding engine—giving organizations more precision and more usable signals for automation at scale. “Address data is never ‘done.

Ready to get started?