New 42-day free trial
Smarty

Helpful Hints to Authenticating Your APIs

In this webinar breakdown, you'll learn some of the most useful tips and tricks to ensure your APIs are authenticated
Andrew Townsend
Andrew Townsend
 • 
November 2, 2022
Tags

We brought out the big guns in the way of our Development Team Lead, Kent Gividen, in a webinar all about authenticating your APIs. He went over some of his most useful tips and tricks that he uses to ensure APIs are authenticated. Was it helpful? You betcha. You wanna get the SparkNotes? Read on.

Common and Not-So-Common APIs to Know About

Kent began by outlining the APIs that he has run into the most in his years as a developer. Some of them he dug into a little deeper than others, but these are all useful to be aware of.

  • REST
    • XML
    • JSON
  • SOAP
    • XML
    • WSDL
  • RPC
  • Proprietary
  • Socket

For the rest of the session he focused on the REST APIs as those are the most common from an HTTP perspective.

Advantages between API and SDK

You can work with APIs raw, and there are benefits to doing so. However, you may find that using an SDK is much easier.

With an SDK you’ll most likely experience a faster startup, you can use one that is code specific, and there may be features built in such as multi-threading, batch modes, and more. You can see a list of Smarty’s SDKs here.

With a raw API you’ll get much more control over how it is implemented, even if that makes your setup a little more tedious. You’ll also be able to use any code base supporting HTTP, which is basically all of them.

Different Types of Authentication

The key to authentication is security. Keeping that in mind you’ll want to know the difference between Embedded keys, which is client side and mobile app focused, or Secret keys which is using a server side key that you do not want to share with people.

You can also use the increasingly popular OAuth, but Kent didn't cover that too deeply. But essentially it’s allowing you to use your login for some services on other services, like logging in with your Google account.

Other Considerations

When you’re using an API you’ll want to make sure you’re using HTTPS with TLS for encryption. You may also want to consider rate limiting. Other things that are becoming more common are nonce, or expiring keys, and proxy servers for additional off-site security. You can pick from several different proxy server options including HA Proxy, Auth0, Okta, etc. This will help you provide an API to your customer that is secure.

Tips and Tricks for Testing Authentication

Kent went through several different tips and tools that he uses to authenticate his APIs. He dives into detail in the recording, but we’ll list a few of them here:

  • curl
  • postman
  • SoapUI
  • Use environment variables for config files
  • shell / command line
  • st / sd / sl

He gave examples of many of these so if you’re curious about any of them you can check out the 6:40 mark in the recording.

Try It Yourself

The latter half of the webinar was filled with fantastic examples and demonstrations of the different ways to authenticate APIs. This is difficult to represent in text, so you’ll probably just want to watch the recording below.

However, if you’d like to try setting up some address validation via an API, you can check 1,000 addresses for free by signing up for a free trial of the Smarty tools, and you can use the API—or any of our SDKs—even on those 1,000 lookups!

Webinar Recording

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
You always need Smarty, unless...
Arrow Icon
We’ll be honest: there are some rare, creative, and oddly inspiring scenarios in which traditional address validation tools—like Smarty—might not be top of mind. Take Gary, for instance. He runs a mail-order sourdough bakery and believes address typos give his shipping process a “personal touch. ” His customers now expect their loaves to go on postal pilgrimages, complete with handwritten notes and breadcrumb trails. Literally. Or Eleanor, who’s lived in the same town for 62 years, ships packages with descriptions like “the blue house with the tire swing near the old Peterson farm.
Why address verification is the necessary complement to autocomplete
Arrow Icon
Address autocomplete is a powerful tool for improving form completions and ensuring users select real, deliverable addresses at entry. However, to maintain long-term data integrity and enhance address-related insights, address verification is a necessary complement. Here’s why:1. Gain up to 55 points of metadata per verified addressAutocomplete provides real-time address suggestions, while address verification appends additional metadata. Address verification enhances each address with up to 55 points of data, such as:ZIP-9 level accuracy geocoordinates (rooftop accuracy also available)ZIP+4 CodesResidential Delivery Indicator (RDI) to identify residential vs.
Property data fuels a Smarty-er search for Sasquatch
Arrow Icon
Bigfoot. Sasquatch. Ol’ Filthy Albert. No matter what you call him, you know who we’re talking about: the hairy giant cryptid who haunts our collective imagination and, according to about 13% of the US population, wanders the American wilderness. The traditional perception of Sasquatch is that of a solitary creature whose run-ins with people are the unavoidable consequence of human development and exploration. If recent sightings are any indication, it seems the legendary creature may have more on their mind than just staying hidden.

Ready to get started?