Pinpoint: A virtual user conference inRegister today
Smarty
    • In this webinar breakdown, you'll learn some of the most useful tips and tricks to ensure your APIs are authenticated

    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 5 address validation use cases ebook nowDownload now
    Read our recent posts
    Around the World in 80 Days (with Smarty!)
    Arrow Icon
    Phony passports. Runaway trains. Rogue elephants. Hot air balloons. Phileas Fogg dodged them all in the 1956 movie adaptation of Jules Verne’s novel, Around the World in 80 Days. His race was against time. Today, your ecommerce business is running a race of its own; delivering quickly, accurately, and affordably across a world full of logistical landmines. Fortunately, you don’t need a valet named Passepartout to guide you (although wouldn’t that be fun?!) You just need Smarty. Smarty is your passport to global address data perfection, specializing in address verification, autocomplete, geocoding, and enrichment.
    Address component analysis: A smarter way to validate addresses
    Arrow Icon
    Most address validation tools give you a simple thumbs up or down on an address because it either matches or it doesn’t, right? But what if you need more than just “valid” or “invalid” as a response? What if you could know exactly what part of the address is off, like a misspelled street name or an unconfirmed vanity city (like Hollywood), and why it isn’t considered valid?What if part of an address needed to change in order to make it a mailable, valid address? We think you’d want to know that, too.
    BREAKING: Rooftop geocodes walk off the job—chaos mounting by the hour
    Arrow Icon
    Dateline: Tuesday, 8:04 a. m. In what experts are calling “the biggest location intelligence crisis since the discovery of space,” rooftop-accurate geocodes have officially gone on strike. The high-precision coordinates—normally pinpointing locations down to the exact rooftop for deliveries, telecom installs, insurance claims, and analytics—appeared on Smarty TV and issued a short but cutting statement this morning:“We’re tired of being taken for granted. We’re tired of being treated like just another number.
    Previous Post
    Next Post

    Ready to get started?

    Schedule Demo
    42-day Free Trial