Account Not Found
account_not_found404
No account matched the credentials in this request. Sign up or verify the sign-in details.
What this means
A dashboard request carried a credential whose account no longer exists: a session or password reset link minted before the account was deleted. Sign-in itself never returns this error; a wrong email or password gets the same authentication_failed whether or not an account exists, so the API never confirms which emails have accounts.
When you'll see this
- A browser tab kept a session for an account that has since been deleted.
- A password reset link was opened after its account was deleted.
Learn more about how this works
A session or reset link points at one account. When that account is gone, the credential can't be used for anything else, so the request stops here. To keep sign-in from revealing which emails are registered, failed sign-ins don't use this error at all.
Example response
{
"success": false,
"error": "account_not_found",
"message": "No account was found matching the provided credentials. Sign up at asterwise.com or verify your sign-in details.",
"details": [],
"retry_after": null,
"doc_url": "https://docs.asterwise.com/reference/errors/account_not_found/",
"request_id": "req_01HXYZABCDEFGH",
"timestamp": "2026-05-25T12:34:56Z"
}
- Sign in again at asterwise.com/signin, or sign up if the account was deleted.
- If you believe the account should still exist, email [email protected] from its address.
Only the dashboard receives this error; API keys never see it, and nothing in an integration needs to handle it.
Production handler
No code example provided.
Avoid this error by
- Sign out of old browser sessions after deleting an account.
- Request a new reset link rather than reusing an old one.