4 blog posts tagged "Technical Support"

Address Verification for Fun and Profit: Using Go SDKArrow Icon
By Andrew Townsend on April 26, 2023
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.
New Feature: Log into Smarty with Your Google AccountArrow Icon
By Davin Perkins on October 11, 2022
New Feature: Log into Smarty with Your Google Account You've asked for it, and now you’ve got it. The next time you log into your Smarty account, you’ll see the option to log in to Smarty using your Google account. Merge an Existing Smarty Account with Google Merging your account with your Google account will not affect your available lookups, security keys, or any other part of your Smarty account. Merging your Smarty account will: * Increase security by reducing the number of managed passwords and how often you have to enter your password.
Common Mistakes When Calling Smarty APIsArrow Icon
By Andrew Townsend on July 28, 2022
There are two types of frequent errors: 401 "Authentication Required" errors, and 402 "Payment Required" errors. Status Code 401 - Authentication Required If you're seeing this error there's a chance that there's an issue with your API key, there's a mistake inside your client-side request, or a mistake in the server-side request. In the recording Lyle dives deep into each of these, but here are the basics. How to Authenticate API Requests It is important that you are familiar with your API keys.
SECURITY ANNOUNCEMENT: Removing Old TLS VersionsArrow Icon
By Jonathan Oliver on October 17, 2019
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 (formerly SmartyStreets) 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.

The leader in location data intelligence

Ready to get started?