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
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?