Common troubleshooting tips
I'm getting 401 errors but my API key looks correct
I'm getting 401 errors but my API key looks correct
Double-check that you’re including the
Bearer prefix in your Authorization header. The format should be: Authorization: Bearer un_live_your_key_here (note the space after “Bearer”). Also verify you’re using the most recent API key from your dashboard.How do I handle rate limiting in my application?
How do I handle rate limiting in my application?
Implement exponential backoff with jitter. Use the
retryAfter field from 429 responses to know exactly when to retry. For high-volume applications, implement request queuing to stay under the 5 RPS limit.Why am I getting empty categories arrays?
Why am I getting empty categories arrays?
An empty categories array means the username is not reserved. Check the
isReserved field - if it’s false, the username is available for use. Only reserved usernames will have categories.My username check returns different results than expected
My username check returns different results than expected
Remember that usernames are automatically normalized (whitespace removed, lowercased). Make sure you’re comparing the normalized username from the response, not the original input. For example,
"New York" becomes "newyork" in the response.Need more help?
If you’re still experiencing issues after reviewing this guide:- Email support: [email protected]
- Check your dashboard: app.username.dev/dashboard for usage stats and API key management
Related documentation
- Error codes - Understand error response formats and how to handle them programmatically
- Error code reference - Detailed information about specific error codes
- Quick start guide - Learn how to make your first API call