API

10 Things You Should Know about Tokens. Couple weeks ago we published a short article about cookies vs tokens in the context of single page applications, in particular applied to AngularJs apps.

It seems the community is interested in this topic, so we published a second article on token based authentication in realtime frameworks like socket.io. There is a great interest in this subject so we decided to continue with an article that explores in more detail some of the most common questions around token-based authentication. So here we go... 1. Tokens need to be stored somewhere (local/session storage or cookies) In the context of tokens being used on single page applications, some people have brought up the issue about refreshing the browser, and what happens with the token.

If you are wondering "but if I store the token in the cookie I'm back to square one". 2. In the world of cookies, there are different options to control the lifetime of the cookie: Cookies can be destroyed after the browser is closed (session cookies).
Radical Transparency - a blog brought to you by the team at Keen IO. Think back to your last job interview for a sec. How important did the interviewer make you feel? How much did they seem to value what you had to offer? Did they value your time more than they valued their own?

If yours was anything like most interviews, your answers probably went something like: 1) Not too important, 2) Not too valued, and 3) Damn sure their time was more valuable than mine. It always amazes me when companies act like you need them more than they need you, when it’s really the other way around. When did building a company become more about the business than about the people? And yet, it still happens. I’ll have the soup, and some backstory, please. I met Kyle Wild in the summer of 2013 in San Francisco during a fundraising trip for my previous startup, Relify.
API Design Training. Create modern apps like never before.
Development Guides. REST API Tutorial. Keen IO - Analytics for Developers. Python Quickstart - Stormpath. Welcome to Stormpath’s Python Quickstart!

This quickstart will get you up and running with Stormpath in about 7 minutes and give you a good initial feel for the Stormpath Python library. During this quickstart, you will do the following: Install the Stormpath library.Create an API Key that allows you to make REST API calls with Stormpath.Register an Application.Create a User Account.Search for a User Account.Authenticate a User Account.

Stormpath also can do a lot more (like Groups, Multitenancy, Social Integration, and Security workflows) which you can learn more about at the end of this quickstart. Let’s get started!
API Introduction - vLine. In order to use the vLine API, you must first create a service in the vLine Developer Console.

Make a note of your Service ID; you'll use it in the next steps. Next, add vline.js to the <head> tag of your HTML: Creating a Client The vline.Client is the top-level interface for using the vLine APIs.
IP Geolocation API Documentation - ipinfo.io. Use the ipinfo.io IP lookup API to quickly and simply integrate IP geolocation into your script or website.

Save yourself the hassle of setting up local GeoIP libraries and having to remember to regularly update the data. Full IP Details When called from the command line or a script we will return a JSON response with all of the IP details that you see on the website.
Paris Is {API}
Delightful Class - Stream. An Introduction to APIs - API Course. About This Course Have you ever wondered how Facebook is able to automatically display your Instagram photos?

How about how Evernote syncs notes between your computer and smartphone? If so, then it’s time to get excited! In this course, we walk you through what it takes for companies to link their systems together. We start off easy, defining some of the tech lingo you may have heard before, but didn’t fully understand. Who Is This Course For? If you are a non-technical person, you should feel right at home with the lesson structure.

When you are finished and before you start coding, we need to collect a few key pieces of information necessary to create an OpenTok application. They are: API key - This identifies your OpenTok account. Session ID - Your session ID identifies the "room" in which participants will meet and chat. Get these from your OpenTok dashboard by following these instructions: Your first project After you login to the dashboard, and click through the Quick Start guide, retrieve your API key from Project A on the Project page. Note: Make sure to copy/paste the whole of the session ID and token.
Webshell - The API Combinator. JIRA REST API Example - Add Comment - JIRA Development. The missing email API to leverage email data. Debug and test your API, webhook and mobile back end service integrations. · Runscope.