When you implement TypingDNA’s Authentication API with the SameText method, you have two ways to capture a typing sample: let users enter any text they like (hoping it is strong enough and that they will reproduce it exactly on future log-ins) or prompt them with a fixed, pre-defined phrase to type. We recommend the fixed phrase because it delivers consistent, high-strength samples for every user. This guide explains how to choose the best text prompt for your app. Although the API can use a unique phrase for each user, the most successful deployments usually stick to one shared phrase for everyone.
1. Start with a natural sentence
Choose something you can type effortlessly and exactly the same every time.
Example: “Children are learning important things in school”
Tips
- 30–40 characters is the sweet spot, but you can use longer texts for higher accuracy.
- NO punctuation, NO special chars needed.
- Keep lower-case as much as possible.
- Use words that make you travel left, right, up and down.
- Avoid passwords or anything you wouldn’t want displayed in plain text.
2. Run it through the strength checker
Type your sentence in the box below and press Enter (or click Calculate Strength):
| Score | What it means |
|---|---|
| 9 – 10 | Excellent variation & balance, a keeper. |
| 7 – 9 | Good, but could be richer, consider tweaking some words. |
| 5 – 7 | Possibly too short, may have some imbalance or repetition |
| < 5 | Too short / repetitive |
3. Refine until you hit 8+
Small edits can boost the score:
| Try this | Why it helps |
|---|---|
| Insert a longer or rarer word | Increases unique-character mix |
| Balance both hands (avoid one-hand strings like “kkk” or “kljk”) | Gives TypingDNA richer timing data |
4. Use with TypingDNA Authentication API (SameText method, type:2 typing pattern)
Once your phrase scores 8 or higher, start using it in your application.
A stronger phrase means fewer false rejections and tighter security, without asking users to re-type.
Happy typing!