Aksha Malik
03/24/2026, 11:11 AMRequest is invalid The user.email field must have a valid domain name - The user.email field must have a valid domain name Error
at Object.error (BaseDescopeWc.js:1:1545)
at Ue.<anonymous> (DescopeWc.js:1:5073)
at Ue.<anonymous> (DescopeWc.js:1:19669)
at Generator.next (<anonymous>)
at fulfilled (tslib.es6.mjs:118:41)
at _ZoneDelegate.invoke (zone.js:398:28)
at ZoneImpl.run (zone.js:113:43)
at zone.js:2537:40
at _ZoneDelegate.invokeTask (zone.js:431:33)
at ZoneImpl.runTask (zone.js:161:47)DevRev
03/24/2026, 11:11 AMsandeep.saini@signitysolutions.in_3 contains an underscore in the domain part, which violates standard email format rules.
Fix the Email Format
1. Remove the underscore from the domain portion:
sandeep.saini@signitysolutions.in3
Or use a different approach like:
<mailto:sandeep.saini+3@signitysolutions.in|sandeep.saini+3@signitysolutions.in>
Alternative Solutions
• Use the plus sign (+) for email variations instead of underscores
• Create separate email addresses without special characters in the domain
• If testing, use a valid test domain format
The error "must have a valid domain name" is triggered by Descope's email validation which follows RFC standards that don't allow underscores in domain names .
Descope Common Errors | Descope DocumentationAksha Malik
03/24/2026, 11:12 AMDevRev
03/24/2026, 11:13 AMsandeep.saini@signitysolutions.in_3 a valid email address because underscores in domain names violate RFC standards that Descope enforces.
Workaround Options
1. Use the Management API instead of flows - it may have less strict validation:
// Management API user creation
const user = await descopeClient.management.user.create({
email: "sandeep.saini@signitysolutions.in_3",
// other user properties
});
2. Create the user with a valid email, then update the loginId:
// Create with valid email first
const user = await descopeClient.management.user.create({
email: "<mailto:sandeep.saini@signitysolutions.in|sandeep.saini@signitysolutions.in>",
loginIds: ["sandeep.saini@signitysolutions.in_3"]
});
Alternative Formats
If you need the "3" identifier, use these valid formats instead:
• <mailto:sandeep.saini+3@signitysolutions.in|sandeep.saini+3@signitysolutions.in> (plus addressing)
• <mailto:sandeep.saini.3@signitysolutions.in|sandeep.saini.3@signitysolutions.in> (dot in local part)
• <mailto:sandeep.saini@signitysolutions3.in|sandeep.saini@signitysolutions3.in> (number in domain)
The underscore in the domain portion will always fail validation as it's not RFC-compliant .
Descope Common Errors | Descope Documentation