Authentication
mockd supports two ways to sign in. You don’t need an account to start using mockd — you can create a project without signing up — but signing in lets you save and manage your work.
Email/Password
Section titled “Email/Password”Create an account with your email and a password on the sign-up page, then sign in with those credentials.
GitHub
Section titled “GitHub”Click Sign in with GitHub to authenticate with your GitHub account. mockd uses the secure PKCE flow for OAuth.
Your GitHub account needs a verified primary email address. mockd reads that address to find or create your account, so it only accepts one GitHub itself has confirmed you own. If your primary address is unverified, sign-in fails with a message asking you to verify it on GitHub first.
Sessions
Section titled “Sessions”After signing in, your session lasts 30 days. You’ll be signed in automatically when you return.
Rate limits
Section titled “Rate limits”To protect accounts and keep mockd off email blocklists, the sign-in surfaces are rate limited. You may see “Too many requests” if you:
- request more than 3 magic links, password resets, or verification emails for the same address within an hour;
- send a large number of those emails from one network within an hour;
- create several accounts in quick succession from the same network.
Limits reset on a rolling one-hour window — wait and try again.
mockd also caps the total number of sign-in emails it sends each day, across all users. This only comes into play during unusual spikes in traffic. While it’s in effect, sign-up, magic-link and verification requests return “Too many requests”, and password reset emails are held back, so if a reset email doesn’t arrive, try again later.