You can see the library documentation by clicking here.

• ✅ World's largest fraud validation database | [email protected] -> Blocked.
• ✅ Fraud validation for personal emails and OAuth (the only one on the market today) | [email protected] -> Blocked.
• ✅ Multi-data validation at no additional cost | Validate email addresses, phone numbers, and more at no additional cost, all in one place.
• ✅ Data normalization | [email protected] -> [email protected] (can be disabled with normalize: false).

Installation

Use one of the following commands to install Dymo API in your TS/JS project.

npm cache clean --force && npm i @dymo-api/better-auth

# or

pnpm cache clean --force && pnpm i @dymo-api/better-auth

# or

yarn cache clean --force && yarn add @dymo-api/better-auth

Authenticating ourselves on the client with the API Key

Get my free API Key

Email Validation

export const auth = betterAuth({
    plugins: [
        dymoEmailPlugin({
            apiKey: "YOUR_API_KEY_HERE",
            emailRules: {
                deny: ["FRAUD", "INVALID", "NO_REPLY_EMAIL"]
            }
            // normalize: true (default) - Set to false to disable email normalization
        })
    ]
});

IP Validation (Experimental)

export const auth = betterAuth({
    plugins: [
        dymoIPPlugin({
            apiKey: "YOUR_API_KEY_HERE",
            ipRules: {
                deny: ["FRAUD", "INVALID", "TOR_NETWORK"]
            }
            // normalize: true (default) - Set to false to disable IP normalization
        })
    ]
});

Phone Validation

export const auth = betterAuth({
    plugins: [
        dymoPhonePlugin({
            apiKey: "YOUR_API_KEY_HERE",
            phoneRules: {
                deny: ["FRAUD", "INVALID"]
            }
            // normalize: true (default) - Set to false to disable phone normalization
        })
    ]
});

More types of validations coming soon to keep you protected.

Frequently Asked Questions

Dymo API normalizes the email by default, removing, for example, the . and + from the email based on the specific provider, which means that if you are not also normalizing the email in the login via OAuth, you will get a mismatch error.

To do this, you have two options: the first and correct one would be to also normalize the login email, and the second would be to disable normalization using normalize: false.