Get your developer account.
Available SDK with code samples.
RESTful API solution for quick integration.
Recognize the user’s true identity on the spot. Our typing biometrics authentication API provides a real-time matching score (numeric 0-100%).
Your end-users don’t have to suffer for added protection. Typing biometrics enables frictionless keystroke authentication in the background of any typed text. Moreover, there is no need for additional browser permissions. In short: No impact on the UX!
TypingDNA supports repetitive text (e.g. login authentication credentials) and any text (e.g. writing an email) recognition, so that you can use it in any typing scenario.
The simple RESTful API and documentation we provide allow developers to deploy in a few days.
Manage API credentials and see advanced stats about the API usage that is performed from your account.
TypingDNA services run on Microsoft Azure Cloud Computing and are built to be easily scalable.
Keystroke authentication provided by TypingDNA works on desktops and smartphones, and supports most languages. Actually, keyboard layouts are mostly the same across different languages.
TypingDNA’s unique approach allows you to authenticate a user starting with only one previous enrollment.
There is no more need for manual identity checks. Verify the identity of millions of users with our automated keystroke dynamics API approach.
Our main “typing pattern” is an array of numbers, keystroke dynamics statistics about 44 keys that are used most of the time.
Any two typing patterns are different, even those from the same individual. In order to perform typing biometrics authentication you need to rely heavily on artificial intelligence/machine learning.
Matching a pattern against others preserving high accuracy, high speed, and low cost is not an easy job.
You have the possibility to try our API for free for a limited time.
Visit our pricing page, for more info.
Any app that wants to authenticate a user needs to have at least one previous keystroke dynamics based typing pattern from that user, that is usually recorded when the user creates a new account.
To perform an authentication the app will record a new pattern (with 2 lines of code, using our JS class) will pass it to their server and will call our REST JSON API with 2 or more patterns.
The API logs the call, verifies the API key and returns the matching result from a worker server that does only matching between 2 or more patterns (a redundant solution with stateless servers).
Once the app gets the result it can decide what to do with it (usually, this is a part of a two-factor authentication system that may also be based on location, cookies, passwords, tokens or other biometrics). More about how it works, see our API documentation.